Dubai Islamic Bank-IT Department

 Style Definition: Heading 3

Business Requirements Document

DIB Mobile Wallet

Created on 01/06/2017 – Document Version: 1

This document of Dubai Islamic Bank-IT Department is a controlled document. Unauthorized access, copying and
replication of this document are prohibited. Changes to this document are permitted only with the prior approval of
the MR and must be applied using the system for control of document, defined for DIB-IT Dept.

INFORMATION TECHNOLOGY DEPARTMENT

P.O.BOX 1080
DUBAI, UNITED ARAB EMIRATES
Tel: 971-4-2075138
Fax: 971-4-2075456

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 1 of 252
 Dubai Islamic Bank-IT Department

Contents

MOBILE WALLET ............................................................................................................................................... 7

DIB SYSTEMS INTEGRATION PRE-REQUISITE ................................................................................................ 8

MOBILE WALLET FEATURES ............................................................................................................................ 9

1. Subscriber Onboarding ........................................................................................................................................................... 10

Self-Service Registration .............................................................................................................................................................. 12
Back-Office / Agent Assisted Registration ............................................................................................................................... 2419
Proposed Onboarding Solution ............................................................................................................................................... 3123
Pilot Onboarding ..................................................................................................................................................................... 3626

2. Linking DIB Accounts and Cards ......................................................................................................................................... 4129

3. Linking 3rd Party Accounts .................................................................................................................................................. 4431

4. Bill Payments........................................................................................................................................................................4532
Payment Sources and Beneficiary .......................................................................................................................................... 4632
Chart of Accounts .................................................................................................................................................................... 4632
Recon/Settlement Files ........................................................................................................................................................... 4733
Biller Notification File .............................................................................................................................................................. 4733
CASA ......................................................................................................................................................................................... 4834
Credit Card ................................................................................................................................................................................5537
Hold Functionality ................................................................................................................................................................... 6039
Wallet SVA................................................................................................................................................................................ 6140
Exception Management .......................................................................................................................................................... 6442
Third Party Accounts ............................................................................................................................................................... 6745

5. Fund / Un-Fund Wallet SVA ................................................................................................................................................ 6846

Fund .........................................................................................................................................................................................6846
Un-Fund .................................................................................................................................................................................... 7249
Closing ....................................................................................................................................................................................... 7551

6. P2P ........................................................................................................................................................................................7853

7. Remit to ATM .......................................................................................................................................................................8557

8. Remittance .......................................................................................................................................................................... 9462

9. Cash in through CCDM........................................................................................................................................................ 9563

10. Cash in / Out through Agent .......................................................................................................................................... 9965

11. Mobile POS Payment ....................................................................................................................................................10066

Create Orders.......................................................................................................................................................................... 10167
Manage Orders ....................................................................................................................................................................... 10971
View Reports............................................................................................................................................................................. 11171

12. Web Checkout ................................................................................................................................................................ 11272

13. Wallet Services ...............................................................................................................................................................11674

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 2 of 252
 Dubai Islamic Bank-IT Department

Transaction Frequency ........................................................................................................................................................... 11674

Configurable Transaction Limits ............................................................................................................................................ 11674

14. Transaction History and Summary Balances ................................................................................................................ 11775

15. System Settings ..............................................................................................................................................................11876

16. App Design ...................................................................................................................................................................... 11977

17. Offers & Deals Catalog .................................................................................................................................................. 12078

BANK PORTAL ............................................................................................................................................ 12179

BANK PORTAL FEATURES ........................................................................................................................ 12280

Maker / Authorizer ................................................................................................................................................................. 12280

1. Administration .................................................................................................................................................................... 12381

User Management .................................................................................................................................................................. 12482
Role Management .................................................................................................................................................................. 12785
Privilege Management ...........................................................................................................................................................12886
User Management Reports ...................................................................................................................................................12886

2. Subscriber Management ................................................................................................................................................... 12987

Enrollment ............................................................................................................................................................................. 13088
Enrollment Queue ................................................................................................................................................................. 13088
Inquire Profile ......................................................................................................................................................................... 13189
Plan Management ................................................................................................................................................................. 151109
Plan Configuration Queue .................................................................................................................................................... 169127
P2P Transactions.................................................................................................................................................................... 171129
P2P Transaction Queue ......................................................................................................................................................... 171129
Refunds Queue ...................................................................................................................................................................... 171129
Unload SVA Queue ................................................................................................................................................................ 171129
Disputes Management .......................................................................................................................................................... 172130
Reports................................................................................................................................................................................... 173131

3. Biller Management ........................................................................................................................................................... 174132

Enrollment ............................................................................................................................................................................. 175133
Enrollment Queue ................................................................................................................................................................ 188138
Inquire Biller .......................................................................................................................................................................... 189139
Plan Management ................................................................................................................................................................ 194144
Plan Configuration Queue .................................................................................................................................................... 199149
Mobile M-POS Management ................................................................................................................................................ 199149
Cut-Offs ................................................................................................................................................................................. 199149
Execute Manual Settlement ................................................................................................................................................ 202152
Cut-Off and Manual Settlement Queue ................................................................................................................................215165
Disputes Management Queue ............................................................................................................................................. 216166
Refunds Queue ..................................................................................................................................................................... 216166
Bank Account Queue ............................................................................................................................................................ 216166
Frequency Queue ................................................................................................................................................................. 216166
Reports................................................................................................................................................................................... 217167

4. Content Management ..................................................................................................................................................... 218168

5. Notification Management ............................................................................................................................................... 220169

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 3 of 252
 Dubai Islamic Bank-IT Department

Notification List ..................................................................................................................................................................... 221170

6. Bank Settings ....................................................................................................................................................................223172

Limit Code Definitions ...........................................................................................................................................................223172

RISK MANAGEMENT ................................................................................................................................ 224173

COMPLIANCE ........................................................................................................................................... 226175

BILLER / AGENT PORTAL ......................................................................................................................... 227176

BILLER PORTAL FEATURES ..................................................................................................................... 228177

7. User Management ........................................................................................................................................................... 229178

User Management ................................................................................................................................................................ 229178
Role Management ................................................................................................................................................................ 229178
Privilege Management ......................................................................................................................................................... 229178
User Management Reports ................................................................................................................................................. 229178

8. Bill Management .............................................................................................................................................................. 230179

Uploading Bills ...................................................................................................................................................................... 230179

9. My Provider Reports ........................................................................................................................................................241187

Upload Receivable Invoices ................................................................................................................................................. 242188
Approve Refunds .................................................................................................................................................................. 242188

Profile Management ................................................................................................................................................................ 243189

10. Create and Publish Catalogs ....................................................................................................................................... 243189

11. Reports .........................................................................................................................................................................244190

12. Dispute Management...................................................................................................................................................245191

AGENT PORTAL FEATURES .................................................................................................................... 246192

APPENDIX A: LIST OF FIGURES ...............................................................................................................247193

APPENDIX B: BILLER LIST....................................................................................................................... 249194

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 4 of 252
 Dubai Islamic Bank-IT Department

Document Sign-Off

Name Position Comments Signature Date

Senior Officer - E-
Hani Khalifa Commerce

Nadeem Gafoor Manager - E-Commerce

AVP - Head of Business

Tareq Bazian
Development

Bicky Advani AVP - Interactive Banking

VP - Head of Express &

Ghalib Hamed Self Service Banking

Khalifa Mohammed VP - Head of Information

Al Shamsi
Security

SVP - Head of Cards

Salman Abedin Loyalty

Amresh Nandkeolyar SVP - Head of Cards

SVP - Head of Electronic

Musabbah Al Qaizi Banking Services & IT

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 5 of 252
 Dubai Islamic Bank-IT Department

Abstract

Dubai Islamic Bank (‘DIB’) is collaborating with PinPay (‘PinPay’) a bill presentment and a payment aggregator based
in Lebanon to jointly host a biller/merchant acquiring platform (EBPP) that will allow companies to present their bills
and products/services on the DIB customer portal (Wallet app, Mobile Banking and Internet Banking) enabling DIB
customer to pay their bills from any of these channels.
The platform also allows hosting of SVA accounts which will be on-boarded via the mobile channel of DIB (Wallet App
to be developed as part of the BRD).
The following engagement model is envisaged:

Channels (DIB or other channels)

 DIB will integrate its channels (Wallet app, Mobile Banking and Internet Banking) to the EBPP platform.
 Allows other partners to integrate with the EBPP platform as separate channels
Issuing Payment Channels
 Each channel will onboard their own issuers to the respective channels. In-case of DIB, the SVA, CASA, CARD
and other payment instruments will be linked to the Mobile Wallet app.
 DIB may also expose its payment channels to other partner channels of PinPay.
Processing and Settlement
DIB will be the exclusive processing partner on the platform for recon and settlement.

Merchants Acquiring
DIB and PinPay will jointly acquire merchants to the platform.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 6 of 252
 Dubai Islamic Bank-IT Department

Mobile Wallet
The purpose of this section of the BRD is to detail the business requirements for the DIB Mobile Wallet project
between Dubai Islamic Bank (DIB) and PinPay.

This document will therefore be illustrating the minimum business requirements for the DIB Mobile Wallet that
would be available in the PinPay mobile platform for DIB.

The main component that will be discussed in this section of the BRD will be the Mobile Wallet. The following back-
office and interface systems will also be discussed within the Mobile Wallet context:

Interface System Components:

 Merchant Mobile POS (M-POS)

 Web Checkout
 DIB ATM/ CCDM
 QubifyOffer and deals portal

Back-Office System Components:

 Payment Gateway to Link 3rd Parties

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 7 of 252
 Dubai Islamic Bank-IT Department

DIB Systems Integration Pre-requisite

The following section will detail the pre-requisites required to perform the systems integration.

ATM/CCDM Emirates ID Check Interface

Subscribers who register as Residents will initially onboard in the pre-KYC state after performing the standard
registration process on the DIB Wallet PinPay app. These subscribers would need to complete a KYC/ID check process
by inserting their valid Emirates ID card at any DIB ATM/CCDM machine.
The details captured from the Emirates ID will be validated against the one entered by customer while registering in
the mobile app locally within DIB systems.
The card details will then be validated by the Emirates ID authority through the validation gateway.

DIB Compliance System

Integration with DIB Compliance System for real-time name screening screening will be part of Phase 2, and in the
pilot phase Offline screening will be –performed by generating a full data dump to be sent to DIB compliance system
daily after EOD in case this feature is available.

Payment Gateway Interface

Integration with an Internet Payment Gateway for authorizing is required to authorize non-DIB cards before linking
them to PinPay DIB mobile wallet and a random amount will be generated as an OTP and validate as two factor.

ICCL Enterprise Loyalty Interface

Maintain consolidated liability of SVA rewards and update the EOD. Keep local reward account and redemption within
PinPay once the subscriber is linked with DIB. The local rewards to be synchronized with DIB enterprise loyalty of the
subscriber, and the local reward account to be disabled.

DIB SOA
All Flex account posting.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 8 of 252
 Dubai Islamic Bank-IT Department

Formatted: Justified

Mobile Wallet Features

This section of the document will detail the different services that can be performed by the subscriber using their
mobile wallet. This includes:

 Subscriber Onboarding
 Linking DIB Accounts and Cards
 Linking 3rd Party Accounts and Cards
 Bill Payments
 Fund / Un-Fund Wallet SVA
 P2P (Sending and Receiving money)
 Remit to ATM
 Remittance
 Cash in through CCDM
 Cash in/out through Agent
 Mobile POS Payment (M-POS)
 Web Checkout
 Wallet Services
 Last Transaction History and Summary Balances
 System Settings
 Offers & Deals Catalog
 App Design

This section of the BRD will therefore describe each individual service offering in detail.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 9 of 252
 Dubai Islamic Bank-IT Department

1. Subscriber Onboarding
There are three different subscriber onboarding workflows to register subscribers to the PinPay DIB Wallet platform.
The onboarding methods detailed have been designed to accommodate the following market segments:

 DIB Customers
 Non-DIB Customers
 Residents
 Visitors

Onboarding Methods:

1. Self-Service Registration
2. Back-Office / Agent assisted Single Registration
3. Back-Office / Agent assisted Bulk Registration

It should be noted that for the back-office initiated onboarding, the process is a dual authentication one that requires
a DIB user to authorize the transaction before it is fully executed.

Additionally, a name screening check will be performed for all registration formats. This process could be an online
check on phase 2, orand it will be sent as a bulk file in pilot phase. In case of the bulk method,Where SVA will be
activated and in parallel the name screening will be performed, and in case name screening fails, the respective SVA
will be blocked.

Pre and Post KYC

Depending on the onboarding method, registering subscribers will either be in the pre or post-KYC state. Each state
will enable the subscriber to perform different functions allowed for that state. Note that each state is a plan that is
configured on the Bank Portal.

When a subscriber is registered, he will automatically be activated with a Wallet SVA account and a Wala’a account:

A. Wallet SVA

The wallet SVA that is activated for the subscriber will be a 16-digit number similar to that of MasterCard and Visa
format. It should be noted that this format will later be aligned with the UBF.

It should be noted that the UBF number will be mapped to the 16-digit SVA number.

B. Wala’a Rewards

The new Wala’a rewards consists of PinPoints Loyalty Points integrating with the Wala’a system. The following
subject will be further discussed with the DIB team.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 10 of 252
 Dubai Islamic Bank-IT Department

 When a subscriber enrolls to the PinPay Wallet service, the Wala’a points will be stored locally within PinPay
Wallet Platform and redeemed locally. A pool balance is updated in the new loyalty system during earning
and redemption.
 Each time a subscriber performs a transaction related to his Wala’a, PinPay Wallet platform will retrieve the
balance.
 The new system will prove a convenient process for third party cards.
 The Wala’a pool balance will be updated in the enterprise loyalty. Therefore if a subscriber links a DIB
account or card, the local points will be synchronized with the enterprise system. The local points account in
this case will be disabled.

For Non-DIB Customers:

For Non-DIB customers, once they have activated their Mobile Wallet, they will be provided with loyalty points that
are stored in the Mobile PinPay wallet platform system.

Inquiring the points balance in this case will be inquired on PinPay’s Wallet Platform’s end, since the points are
stored there.

For DIB Customers:

For DIB customers, after they have linked their DIB accounts, there must be a synchronization process to merge the
subscriber’s existing loyalty account located at ICC DIB DIB enterprise loyalty system to the one available at the
PinPay Wallet Platform system. Once merged, the PinPay Wallet Platform system will freeze the local points on its
end and use the consolidated account located at DIB enterprise loyalty system. All redemption will happen in the
central account at DIB enterprise loyalty system.

Inquiring the points balance in this case will be inquired at DIB enterprise loyalty system, since the loyalty points are
stored there.

Subscribers will then be able to redeem their points at PinPay’s Wallet’s channel and on all other DIB’s channels.

In Summary:
 DIB will purchase the points balance from the PinPay systemWallet Platform.
 The DIB subscriber will have the option to redeem his points from the PinPay Wallet Platform channel or
from other DIB channels
DIB will be using the PinPay Wallet Platform system as an intermediary to convert any points into Wala’a
Dirhams
Earn and redeem loyalty from ICC system for Wallet earn through wallet and redeem other points in wallet
Shift loyalty points to enterprise loyalty when a wallet is linked to DIB CIF, and verify the shift of points from
SVA DB to ICC
 Loyalty event triggers definition to be maintained in Wallet Platform and configurable by DIB users.

Note: An interface to deal with third parties’ points’ conversion will need to be discussed later.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 11 of 252
 Dubai Islamic Bank-IT Department

Self-Service Registration

The self-registration process enables subscribers to enroll themselves to the PinPay Wallet platform directly on the
PinPay Wallet app.

Both residents and visitors can onboard themselves.

The registration process is therefore divided into the following workflows:

DIB Customers
Non-DIB Customers
Residents
Visitors

DIB Customer Workflow

DIB existing customers can onboard themselves on the Wallet app without the need to undergo a KYC process, as they
are already existing bank customers.

Step 1
Subscriber downloads the mobile wallet app and verifies his device by entering his UAE mobile number and requesting
a verification code. The code is received via SMS and is entered into the app along with an M-PIN.

Step 2
Subscriber must then select on the app whether he is a DIB customer or not.

Step 3
Subscriber selects that he is a DIB customer and will be required to enter his Debit Card Number and PIN. The request
is forwarded, where the data is validated. A response is returned back to the hosted page. The Wallet App then
requests a confirmation from the DIB system to ensure that the information was received and validated.

Step 4 – Generate OTP

DIB will generate an OTP on its end and sent it to the subscriber’s device via SMS. It should be noted that DIB will send
the OTP to the subscriber’s mobile number that is saved on DIB core system. This number is linked to the subscriber’s
portfolio and is extracted based on the Debit Card information entered.

Step 5 – Enter OTP

The subscriber will then enter the OTP on the Wallet App and submit it. The request is sent to Wallet Platform and
forwarded to DIB via the Member Center. The bank then authenticates the OTP before sending confirmation back to
the Member Center.

Step 6
Once DIB returns a successful confirmation, Wallet Platform will request the user’s list of linked accounts from the DIB
System.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 12 of 252
 Dubai Islamic Bank-IT Department

Step 7
DIB returns the list of accounts (along with the account details) to link back to the Wallet Platform, before they are
displayed on the Wallet App for the user to select and link. The subscriber must select which account/cards he wishes
to link and then submit his request.

Step 8
The request is received by Wallet Platform and stores the following information on its end for each account/card and
is displayed on the Wallet App. Therefore, each account/card linked will be displayed on the app with their balances.

The subscriber is notified via SMS and Email of the successful account/card linking.

Step 9
After linking the accounts, the subscriber is taken to the home screen of the Wallet app.

Note that the above workflow wireframe is available in the “Linking DIB Accounts and Cards” section of the document. Formatted: Justified

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 13 of 252
 Dubai Islamic Bank-IT Department

Residents Workflow (Non-DIB Customers)

Residents who register themselves to the PinPay Wallet platform will automatically be enrolled in the Pre-KYC state.
He must then validate his Emirates ID at any DIB ATM to complete the KYC process (ATM EIDA validation is phase 2).

Pre-KYC Process (Phase 1):

Step 1
Subscriber downloads the PinPay mobile wallet app and verifies his device by entering his UAE mobile number and
requesting a verification code. The code is received via SMS and is entered into the app along with an M-PIN.

Step 2
Subscriber must then select on the app whether he is a DIB customer or not. The subscriber selects that he is a New
Customer (therefore not a DIB customer).

Subscriber must then select on the app whether he is a Resident or a Visitor.

Step 3
Subscriber selects on Resident. He then scans his Emirates ID on the app, and it captures the Emirates ID number and
Full Name from the card itself. The subscriber then clicks on Next.

In the subsequent screen, the subscriber He must then fill in the following information on the app:

First screen info:

 First and Last Name (pre-filled from the Emirates ID scan)
 Mobile Number
 Email
 Nationality
 Birthday

Second screen info:

 Residency Type (Resident)
 Document Type (Emirates ID) – pre-filled from the Emirates ID scan
 Document ID – pre-filled from the Emirates ID scan
 Expiry Date

Step 4
Subscriber submits the information. The request is sent to the PinPay Member Center and is forwarded to DIB’s
System. The following checks are then performed on DIB’s end:

 As part of Phase 1 Online Name check (this process could alsowill be sent as a batch file)
o In case the name screen will happens as a batch file, , SVA will be created and activated and in parallel
the name screening will be performed, and in case name screening fails, the respective SVA will be
blocked
o The name screening process is planned to be performed every 4 hours. The subscriber will also be
notified to visit an ATM to complete the KYC.
Emirates ID information check (this process will validate the Emirates ID data)
 For Phase 2 the Screening process will real-time through an online integration with DIB compliance system

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 14 of 252
 Dubai Islamic Bank-IT Department

Step 5
If any of the above checks fails validation, the request is sent to the back-office queue for revision by someone at DIB
back office user.

Step 6
If the all validation checks proves successful, Member Center is notified and the subscriber is registered in the Pre-KYC
state. His wallet is activated and the subscriber can perform any activities allowed within the Pre-KYC Entry plan.

Step 7
The subscriber is notified by Email and SMS to complete the KYC process on any DIB ATM. All these notifications will
be routed through DIB’s gateway.

Post-KYC Process (Phase 21):

Step 1
Subscriber enters his mobile number onto the DIB ATM and scans his Emirates ID.

Step 2
In Phase 1 DIB system will read the details stored in the Emirates ID and validate it against the data entered in the app
locally and if validation pass, data will be stored and subscriber moved to post KYC stage.
In Phase 2 Thethe DIB System receives the request and performs a check on the Emirates ID. If the details are valid
for the subscriber, the Emirates ID information are stored in the database.

Step 3
If the information is not valid, the issue is logged at the Bank Portal for further review by DIB.

If the information is valid, the subscriber will be moved to the Post-KYC state.

Step 4
A welcome notification is sent to the subscriber via Email and SMS informing him of the successful registration. He can
now link his DIB accounts and credit cards.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 15 of 252
 Dubai Islamic Bank-IT Department

Figure 11 - Resident Self-Registration (Pre KYC) Formatted: Normal

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 16 of 252
 Dubai Islamic Bank-IT Department

Field Code Changed

Resident Self-Registration – Pre KYC
DIB Wallet Wallet Platform DIB System

User enters UAE

Performs validation
Mobile Number and
1 checks on request
requests
and user
Verification Code

User selects to
2.
register as Resident

Receives request and

User enter Receives Request
performs the checks:
Application Form 4 and forwards it to 5
- Name screening
details DIB
- Emirates ID info

Issue is logged at
Bank Portal for Validation
7. No
further review by Successful?
DIB

Receives Response 7. Yes

Onboarding
Subscriber is
successful and
notified to complete 9
subscriber is in Pre-
KYC process
KYC state
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 17 of 252
 Dubai Islamic Bank-IT Department

Resident Self-Registration – Pre KYC

PinPay App PinPay DIB System

User enters UAE

Performs validation
Mobile Number and
1 checks on request
requests
and user
Verification Code

User selects to
2
register as Resident

Receives request and

User enter Receives Request
performs the checks:
Application Form 4 and forwards it to 5
- Name screening
details DIB
- Emirates ID info

Issue is logged at
Bank Portal for Validation
7. No
further review by Successful?
DIB

Receives Response 7. Yes

Onboarding
Subscriber is
successful and
notified to complete 9
subscriber is in Pre-
KYC process
KYC state
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 18 of 252
 Dubai Islamic Bank-IT Department

Figure 22- Resident Self-Registration (Post KYC)

Field Code Changed
Resident Self-Registration – Post KYC
Formatted: Font: 11 pt, Not Bold, Italic
DIB ATM DIB System Wallet Platform

User enters his

1 Receives request
Mobile Number

Validate if Mobile Entered

has active pending record
for EIDA Validation in
Platform

Has Pending
4. Yes 4. No Request is rejected
Record?

ATM opens slot to

accept EIDA

Stores Emirates ID
Emirates ID
information and all
5 information 6
public info from card
captured
into the Platform

Onboarding
successful and
subscriber is in Post-
KYC state

Notification sent to
subscriber
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 19 of 252
 Dubai Islamic Bank-IT Department

Formatted: Justified
Resident Self-Registration – Post KYC
DIB ATM DIB System PinPay

User enters his

Mobile Number and
1 Receives request
scans his Emirates
ID

Checks if the info

received is valid

Issue is logged at
Bank Portal for
Info Valid? 4. No
further review by
DIB

4. Yes

Onboarding
Stores Emirates ID
successful and
5 information in the
subscriber is in Post-
database
KYC state

Notification sent to
subscriber
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 20 of 252
 Dubai Islamic Bank-IT Department

Visitors Workflow (Non-DIB Customers)

Visitors who register themselves to the PinPay wallet platform will automatically be enrolled in the Pending
Verification Mode. A back-office officer must then validate his Passport (and if necessary, his Visa) in order to
complete the KYC process.

Step 1
User enters UAE Mobile Number and requests a verification code. After inserting it into his device, the request is
submitted and PinPay DIB Wallet Platform performs a validation check on the subscriber.

Step 2
Subscriber must then select on the app whether he is a DIB customer or not. The subscriber selects that he is a New
Customer (therefore not a DIB customer).

Subscriber must then select on the app whether he is a Resident or a Visitor. He selects on Visitor.

Step 3
User enters the application form details and uploads an image of his Passport and Visa (if required). The user submits
the information entered. The data is forwarded from the Member Center to DIB.

First screen info:

 First and Last Name
 Mobile Number
 Email
 Nationality
 Birthday

Second screen info:

 Residency Type (Visitor)
 Document Type (Passport. He also takes a picture of the first and last page of the passport).
 Document ID
 Expiry Date

Third screen info:

 Home address and contact details

At this point, the subscriber is in the Pending Verification Mode. He receives a welcome message via SMS and email
informing him that his application is being processed.

Step 4
The onboarding request is submitted and logged in the Bank Portal Subscriber Enrollment Queue. A DIB back-office
user officer reviews and verifies the information submitted. The following checks are performed:

 Online Name check (this process could also be sent aswill be a batch file in pilot phase)
o In case the name screen happens as a batch file, SVA will be activated and in parallel the name
screening will be performed, and in case name screening fails, the respective SVA will be blocked.
 Passport information check (this process will validate the Passport data)

Step 5

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 21 of 252
 Dubai Islamic Bank-IT Department

The response is forwarded back to DIB Wallet platform DIB. If the information submitted fails the validation, the
issue is forwarded back to the Member Center is logged at the Bank Portal (back-office) for further review by DIB
Back office user.

Step 6
If the all validation checks proves successful, the Member Center is notified and the subscriber is registered in the
Post-KYC state.

Step 7
The subscriber is notified by Email or SMS of the successful registration. He can then add his DIB account and cards.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 22 of 252
 Dubai Islamic Bank-IT Department

Figure 33- Visitor Self-Registration

Formatted: Normal
Visitor Self-Registration Field Code Changed
Formatted: Font: 11 pt, Not Bold, Italic
DIB Wallet Wallet Platform DIB System

User enters UAE

Performs validation
Mobile Number and
1 checks on request
requests
and user
Verification Code

User selects to
2. Response sent to Wallet App
register as a Visitor

User enter
Application Form Back-office officer
Receives request
details and uploads performs a check on the
and logs the
Passport/Visa Pic passport and name
onboarding request 6
in the Onboarding
DIB System will perform
Queue
an Online Name Check
4
5

User acknowledge 7
request via App
Confirmation
screen/Notification
Issue is logged at
Bank Portal for
User is in Pending 8. No Is the Info Valid?
further review by
Verification Mode DIB

8. Yes

Receives Response
Receives Response 9. Yes and forwards it to
Wallet Platform

10

Subscriber is Onboarding
notified of successful and
11
successful subscriber is in Post-
registration KYC state
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 23 of 252
 Dubai Islamic Bank-IT Department

Visitor Self-Registration
PinPay App PinPay DIB System

User enters UAE

Performs validation
Mobile Number and
1 checks on request
requests
and user
Verification Code

User selects to
2. Response sent to PinPay App
register as a Visitor

User enter
Application Form Receives request
details and uploads and logs the Back-office officer
Passport/Visa Pic 4 onboarding request 5 performs a check on the
in the Onboarding passport and name
User is in Pending Queue
Verification Mode

Issue is logged at
Bank Portal for
7. No Is the Info Valid?
further review by
DIB

7. Yes

Receives Response
Receives Response 8. Yes and forwards it to
PinPay

Subscriber is Onboarding
notified of successful and
10
successful subscriber is in Post-
registration KYC state
Phase

Back-Office / Agent Assisted Registration

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 24 of 252
 Dubai Islamic Bank-IT Department

The back-office and agent assisted registration process enables the bank or agent to enroll subscribers to the PinPay
wallet platform directly through the Bank Portal and/or Agent Portal.

The Bank/Agent can therefore enroll both residents and visitors can onboard themselves.

They can therefore enroll subscribers individually or in bulk.

Residents/Visitor Individual Workflow

Residents and Visitors can visit any DIB bank or agent in order to register to the PinPay platform Wallet Platform. In
this process, a back-office officer will be manually filling in the information to the Bank Portal.

Step 1
If the subscriber is a Resident, he would fill in the application form at DIB/Agent and submits the form as well as his
Emirates ID (copy and original).

If the subscriber is a Visitor, he would fill in the application form at DIB/Agent and submits the form as well as his
Passport copy (and visa if required).

Step 2
DIB/Agent fills in the application details on the Bank Portal and submits the onboarding request. There will be an ID
validation machine at the DIB bank/agent to capture the subscriber’s ID details.

Step 3
The details is received by DIB System (SOA). The subscriber is notified by SMS and Email that his application is being
processed. (The information received is thenis then forwarded to the Emirates ID Authorizer entity to validate the
information submitted) phase 2.

Step 4
The response is forwarded back to DIB. If the information submitted fails the validation, the issue is forwarded back
to the Member Center is logged at the Bank Portal for further review by DIB back office user. The DIB Back office ank
user can either reject or accept the enrollment request. He will be able to add his comments before submitting his
decision.

If the information submitted passes the validation checks, the bank would be required to perform a manual online
name screening check. Note that this process may possibly bewill be a bulk file sent on a periodical basis in phase 1.
This can be further elaborated between DIB and PinPay.

In case the name screen happens as a batch file, SVA will be activated and in parallel the name screening will be
performed, and in case name screening fails, the respective SVA will be blocked.

Step 5
If the name screening validation fails, the issue is forwarded back to the Member Center to be logged at the Bank
Portal for further review by DIB. The DIB bank user will then either reject or accept the request, and include his
comments when submitting his decision.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 25 of 252
 Dubai Islamic Bank-IT Department

If the name check validation passes, the response is forwarded back to the Member Center. The Onboarding is
flagged as successful and the subscriber’s wallet is activated. He is now in the Post-KYC state and link his DIB
accounts/cards.

Note that the DIB Bank user can access a list of reports related to the subscriber onboarding, approval audit, online
failure review audit etc. Please refer to the Bank Portal section in the BRD for a list of these reports.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 26 of 252
 Dubai Islamic Bank-IT Department

Figure 44 – Resident/Visitor Back-Office Registration - Individual

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 27 of 252
 Dubai Islamic Bank-IT Department

Resident/Visitor Back-Office - Individual

DIB Branch/Agent PinPay DIB System

Resident: DIB/Agent fills in the

User fills in application application details
1 on the Bank Portal
form, attaches Emirates
ID copy and submits it
DIB/Agent 2

Visitor: Back-office officer

User fills in application DIB/Agent submits
3 performs a check on the
form, attaches Passport onboarding request
information received
Copy and submits it to
DIB/Agent
4

Issue is logged at
Bank Portal for
5. No Info Valid?
further review by
DIB

5. Yes

Back-office officer
Subscriber is Onboarding
has option of
notified of the successful and
9 8. If Accept accepting or
successful subscriber is in Post-
rejecting the
registration KYC state
enrollment

Subscriber is
notified of the failed 9 Onboarding Failed 8. If Reject – Officer includes his comments
registration
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 28 of 252
 Dubai Islamic Bank-IT Department

Field Code Changed

Resident/Visitor Back-Office - Individual
DIB Branch/Agent Wallet Platform DIB System

Resident: DIB/Agent fills in the

User fills in application application details
form, attaches Emirates 1 on the Bank Portal
ID copy and submits it
DIB/Agent 2

Visitor: Back-office officer

User fills in application DIB/Agent submits
3 performs a check on the
form, attaches Passport onboarding request
information received
Copy and submits it to
DIB/Agent
4

Issue is logged at
Bank Portal for
5. No Info Valid?
further review by
DIB

5. Yes

Back-office officer
Subscriber is Onboarding
has option of
notified of the successful and
9 8. If Accept accepting or
successful subscriber is in Post-
rejecting the
registration KYC state
enrollment

Subscriber is
notified of the failed 9 Onboarding Failed 8. If Reject – Officer includes his comments
registration
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 29 of 252
 Dubai Islamic Bank-IT Department

Residents/Visitor Bulk

The back-office service center/agent can onboard subscribers in bulk by uploading the file on the bank portal. The
passport/Emirates ID should be validated prior to the generation of the bulk file.

The process flow is therefore the same as the Residents/Visitor Individual workflow, with the exception that the
DIB/Agent user will generate a bulk file of the validated subscribers and upload it to the bank portal to activate the
subscribers’ wallets.

Note that the bulk registration process will not be available in Phase 1 of the project.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 30 of 252
 Dubai Islamic Bank-IT Department

Proposed Onboarding Solution (Phase 2)

The proposed onboarding solution has been designed to provide a unified process flow to onboard DIB customers
through all available DIB channels, including:

 Mobile Banking App

 Online Banking interface
 DIB ATM

The concept behind the proposed unified workflow is based on the DIB customer applying for the PinPay Wallet service
through a secure DIB channel that the subscriber must initially log into in order to register.

This solution would therefore just require a single API that would be called to execute the onboarding process,
regardless of the channel.

Step 1
Precondition: Subscriber must already have his device verified and profile created (standard PinPay Wallet
registration once app is downloaded).

Step 2
Subscriber securely accesses the DIB bank channel and selects on the “Link PinPay’ Wallet’ service.

Step 3
The request is sent to the DIB System, which then compiles the subscriber’s information and sends them to the
PinPay Wallet Platformsystem. The information required are:

 CIF
 Full Name
 Mobile Number
 Email
 Bank Channel that the request was initiated from

Step 4
Information is received and stored at PinPay’s Wallet’s database. PinPay Wallet platform then generates a code
based on the information received and submits it to DIB’s System.

Step 5
DIB receives the Code and forwards it to the DIB Channel. The code is displayed on the banking channel for the
subscriber to scan (if barcode) or manually enter it on his PinPay Wallet app.

Step 6
After entering/scanning the code, the request is sent to the PinPay systemWallet Platform. PinPay The Wallet
Platform then validates the information received and matches it with the information already stored in the database.

If the validation is successful, the subscriber is registered successful. The Wallet PlatformPinPay then notifies the
bank and subscriber.

Step 7

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 31 of 252
 Dubai Islamic Bank-IT Department

The subscriber can now link his DIB accounts. He accesses the Wallet and selects to Add DIB Accounts. He then
enters the DIB Debit Card Number and PIN in order to retrieve all available accounts. This process is further
explained in the next section of this document (Linking DIB Accounts and Cards).

Note that you can use the same process to link additional accounts.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 32 of 252
 Dubai Islamic Bank-IT Department

Figure 55 - Unified Onboarding Workflow

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 33 of 252
 Dubai Islamic Bank-IT Department

Unified Registration Workflow (Phase 2)

PinPay App DIB Channel DIB System PinPay

User registers to the

PinPay app and
verifies his device

User profile is User securely

created and is now 2 accesses DIB
verified Channel

User selects on
Link PinPay 4 Request received
button

Sends the following

subscriber info to PinPay
System:
- CIF Stores the info
- Mobile Number 6 received in the
- Email database
- Full Name
- Channel that the call was
initiated on
7

Subscriber scans or
Receives Code and Generates a code
manually enters the Code displayed on
10 9 submits it to the DIB 8 and sends it to the
code on the PinPay the DIB channel
channel DIB system
app

11

Receives request
and compares data
Request is sent to
12 received to
the PinPay system
subscriber info
stored

13

Subscriber is
Subscriber selects Bank is notified of
validated and is now
on add DIB the successful 14
successfully
Accounts registration
registered
14
15

Subscriber enters
his DIB Debit Card
and PIN
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 34 of 252
 Dubai Islamic Bank-IT Department

Field Code Changed

Unified Registration Workflow
DIB Wallet DIB Channel DIB System Wallet Platform

User registers to the

DIB Wallet and
verifies his device

User profile is
User securely logs
created and is now
into the DIB Channel
verified

User selects on
Request received
Link Wallet button

Sends the following

subscriber info to Wallet
Platform:
- CIF Stores the info
- Mobile Number received in the
- Email database
- Full Name
- Channel that the call was
initiated on

Subscriber scans or
Receives Code and Generates a code
manually enters the Code displayed on
submits it to the DIB and sends it to the
code on the Wallet the DIB channel
channel DIB system
app

Receives request
and compares data
Request is sent to
received to
the Wallet Platform
subscriber info
stored

Subscriber is
Subscriber selects
validated and is now
on add DIB
successfully
Accounts
registered

Subscriber enters
his DIB Debit Card
and PIN
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 35 of 252
 Dubai Islamic Bank-IT Department

Pilot Onboarding

During the pilot stage, DIB bank users will be able to register to the Wallet service and will automatically be taken to
the Post-KYC state after entering their Debit Card and PIN.

For the pilot:

The user will not be required to scan his Emirates ID at a DIB ATM.
The user must enter his Emirates ID details on the Wallet app in order to validate the format and logic of the
card information.
For the pilot stage of the DIB Wallet project, considering that there might be a possible delay in delivering the ATM
Emirates ID card solution, the pilot onboarding process will be similar to the one implemented in the POC stage.

The pilot onboarding process may therefore skip one of the following systems – this will be decided later:

 Online name screening

 ATM KYC
 Debit Card entry and PIN

The process below will therefore enable the onboarding process of DIB customers using the same workflow applied
during the POC stage.

Workflow

Step 1
Subscriber downloads the Wallet app and verifies his device by entering his UAE mobile number and requesting a
verification code. The code is received via SMS and is entered into the app along with an M-PIN.

Step 2
Subscriber must then enter his Emirates ID number and birthday and submit the request.

Step 3
The Emirates ID format and info is validated on the app.
If the validation is successful, the user is taken to the Home Screen of the Wallet App
If the validation fails, the subscriber will be notified of the failure on the app and will not be able to proceed
to the next screen.
Step 14 – Select DIB Account type
The subscriber must initially select select to add DIB as an Account type on the PinPay Wallet app. He would then
need to enter the following information:
 Debit Card Number
 PIN Code (this should be the PIN code for the Debit Card entered)

After submitting the information, the request is sent to PinPay and forwarded to the DIB System through the
Member Center for processing and validation checks.

Step 25 – Generate OTP

DIB will generate an OTP on its end and send it to the subscriber’s device via SMS. It should be noted that DIB will
send the OTP to the subscriber’s mobile number that is saved on its DIB Core system. This number is linked to the
subscriber’s portfolio and is extracted based on the Debit Card information entered.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 36 of 252
 Dubai Islamic Bank-IT Department

Step 63 – Enter OTP

The subscriber will then enter the OTP on the PinPay Wallet app and submit it. The request is sent to PinPay Wallet
Platform and forwarded to DIB via the Member Center. The bank then authenticates the OTP before sending
confirmation back to the Member Center.

Step 4 7 – Request Subscriber Portfolio

A second call is sent from the Member Center to DIB requesting the subscriber’s full portfolio. DIB will send back the
following subscriber information to PinPayWallet Platform:
 Mobile Number
 CIF
 Customer Segmentation
 Full Name
 Email Address

Step 5 8 – Create DIB Profile and Wallet SVA

The Member Center will store the subscriber’s portfolio and create the subscriber’s DIB profile and Wallet SVA.
The Member Center will then notify the PinPay SystemWallet PlatformWallet Platform of the successful registration.
The PinPay SystemWallet Platform will then send a confirmation message to the PinPay Wallet app to notify the user
that his registration was successful.

Step 6 9 – Subscriber Selects Linked Accounts

The Member Center will then request the subscriber’s linked account types from DIB. DIB returns the subscriber’s
linked accounts including the Walla back to the Member Center.

The subscriber will then select which accounts he wants to link from the list of available accounts that was retrieved.
Each time that the subscriber enters his debit card number and PIN, a request is sent to retrieve a list of his account
types.

He should be able to select which account type is the default one.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 37 of 252
 Dubai Islamic Bank-IT Department

Figure 66 - Create DIB Profile and Wallet SVALink DIB AC/Card – Existing Users
 Dubai Islamic Bank-IT Department

Link DIB AC/Card Formatted: Keep with next

Subscriber DIB Wallet Wallet Platform Member Center DIB System Field Code Changed
Formatted: Font: 11 pt, Not Bold
Processes & sends
User selects on DIB Enters Debit Card Sends request to Performs checks
1 2 request to Bank 3 4
as Funding Source Number and PIN DIB System and validation
Portal

Invalid Card
Blocks the User 6. Yes
Entry = 3

Receives Validation
Response as 6. No
Successful
6. No

Receives OTP via

7. Sends OTP to Subscriber s Mobile Number (that is already available in the system) Generates OTP
SMS

Enters OTP on Sends OTP to Sends OTP to DIB

8 9 10 11 Authenticates OTP
Wallet App Member Center for authentication

Request
Subscriber 12. Sends confirmation
Portfolio

13

Sends Subscriber Portfolio to Wallet

Platform:
- Mobile Number
- CIF
Stores - Customer Segmentation
Notify subscriber of
successful linking
15 Subscriber s 14
funding sources If user is New:
- Transfer all Wala a stored Loyalty to
DIB Loyalty System ICC
- Direct to DIB loyalty System ICC for all
future transactions (earn/burn)
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 39 of 252
 Dubai Islamic Bank-IT Department

DIB Profile and Wallet SVA

Subscriber PinPay App PinPay System Member Center DIB System

Processes & sends

User selects on DIB Enters Debit Card Sends request to Performs checks
1 2 request to Bank 3 4
as Funding Source Number and PIN DIB System and validation
Portal

Receives OTP via

6. Sends OTP to Subscriber s Device Generates OTP
SMS

Sends OTP to Sends OTP to DIB

7 Enters OTP on App 8 9 10 Authenticates OTP
Member Center for authentication

Request
Subscriber 11. Sends confirmation
Portfolio

Sends Subscriber Portfolio to

PinPay:
12 - Mobile Number
- CIF
- Customer Segmentation

Creates
Notify subscriber
Sends confirmation subscriber s DIB
that registration is 15 14 13
to PinPay App profile and Wallet
successful
SVA

Request Sends PinPay

subscriber s 16 subscriber s linked
funding sources funding sources

Subscriber selects Stores

which funding 18 Subscriber s 17
sources to link funding sources
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 40 of 252
 Dubai Islamic Bank-IT Department

Formatted: Indent: Left: 0.25", No bullets or numbering

2. 2. Linking DIB Accounts and Cards
DIB customers can easily link their DIB accounts and cards on the PinPay Wallet app as they are in the post-KYC state.
Once they have linked their accounts, they can then perform transactions and execute payments through any of the
linked accounts.

In order to link the DIB accounts and cards the customer need to enter the card details (card number and PIN) in the
Mobile wallet app and same will be validated and upon successful validation the customer will be able to proceed.

Workflow

Step 1
User selects “Link DIB Account”

Step 2
User enter the card number and Pin.

Step 3
The request is forwarded, where the data is validated. A response is returned back to the hosted page. The PinPay
Wallet app then requests a confirmation from the DIB system to ensure that the information was received and
validated.

Step 4 – Generate OTP

DIB will generate an OTP on its end and send it to the subscriber’s device via SMS. It should be noted that DIB will send
the OTP to the subscriber’s mobile number that is saved on DIB core system. This number is linked to the subscriber’s
portfolio and is extracted based on the Debit Card information entered.

Step 5 – Enter OTP

The subscriber will then enter the OTP on the Wallet app and submit it. The request is sent to Wallet Platform and
forwarded to DIB via the Member Center. The bank then authenticates the OTP before sending confirmation back to
the Member Center.

Step 46
Once DIB returns a successful confirmation, PinPay Wallet Platform will request the user’s list of linked accounts
from the DIB system.

Step 57
DIB returns the list of accounts (along with the account details) to link back to the PinPay system Wallet Platform,
before they are displayed on the PinPay Wallet app for the user to select and link. The subscriber must select which
account/cards he wishes to link and then submit his request.

Step 68
The request is received by PinPayWallet Platform. PinPay And stores the following information on its end for each
account type selected by the subscriber:
 Account Type
 Name of Account
 Shadow Account Number
 For debit/credit cards, PinPay Wallet Platform stores the Encrypted CardCare Number

Step 79
 Dubai Islamic Bank-IT Department

Once the accounts have been linked, a get balance request is sent to DIB for each linked account/card and is
displayed on the PinPay Wallet app. Therefore each account/card linked will be displayed on the app with their
balances.

The subscriber is notified via SMS and Email of the successful account/card linking.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 42 of 252
 Dubai Islamic Bank-IT Department

Figure 7 - Linking DIB Accounts and Cards

Linking DIB Cards and Accounts
PinPay App Hosted Page DIB System PinPay System

User selects Link Displays redirection

1
DIB Account Debit Card screen

User enters Debit

Card number and
PIN

Forwards response Validates data

4
to DIB System received

Sends a
Forwards response Returns response
confirmation 7 6
to PinPay app back to hosted page
request to DIB

Confirms the
8 request as
successful

Request linked
9
accounts

Fetch linked
10 accounts from DIB
system

DIB returns the list

11
of accounts to link

Receives linked
accounts and
12
returns them to the
PinPay App

Displays linked
13
accounts to user

14

User selects PinPay stores the

15
accounts to link linked account
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 43 of 252
 Dubai Islamic Bank-IT Department

3. Linking 3rd Party Accounts

Subscribers can easily link their non-DIB accounts and cards on the PinPay Wallet app as they are in the post-KYC
state. Once they have linked their accounts, they can then perform transactions and execute payments through any
of the linked accounts.

Payment Gateway
To link a third party card and account, the subscriber must enter his card information on the PinPay Wallet app. This
process is done through a payment gateway provided by DIB to authorize the card linking.

A validation process will check whether the card details entered belongs to DIB or not. If it does, the subscriber will
be rerouted to the DIB linking flow.

Validation for a non-DIB bank card will be done by debited a random specific amount for authorization. The
subscriber will then be asked to enter the specific amount that was debited into the app.

This process will not be included in phase 1. This workflow still needs to be discussed on how to manage the settlement
and refund processes for non-DIB cards.
This function is part of Phase 1

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 44 of 252
 Dubai Islamic Bank-IT Department

4.1. Bill Payments

Subscribers can conduct different types of bill payments through the PinPay Wallet app. This extends to product
purchases, vouchers, prepaid services, postpaid bills, blind bill payments and so on.

This section will therefore cover the bill payment accounting workflows that the transaction will run through when the
subscriber conducts a payment using his Wallet SVA, CASA, Credit Card and Wala’a accounts.

Note that for all payment requests, PinPay Wallet Platform will initially send an inquiry to DIB to check if the subscriber
has sufficient funds in his accounts.

The following should be noted:

 Hold – DIB performs a hold on the subscriber’s account until the Claim File is received by the Wallet System.

 Claim File – The Wallet System will send this file at the end of the day along with the Settlement file to
inform DIB of the successful service rendered from the biller’s end. DIB will then release its hold on the
subscriber’s account and perform multiple debit and one consolidated credit to PinPay Pool account .

 Authorization – the authorization process done at DIB’s end is to check whether the subscriber has sufficient
funds in his account. After checking whether the subscriber has sufficient funds, DIB will send the Wallet
System an authorization message. No funds are moved here on DIB’s end – funds are only moved once the
relevant end of day files are received from the Wallet System.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 45 of 252
 Dubai Islamic Bank-IT Department

Payment Sources and Beneficiary

Subscribers can perform different types of transactions from each of their account types. The matrix below details the
funding source and beneficiary:

Account Type Beneficiary

P2P, Remit2ATM, Bill Payment, POS Payment, Remittance,
SVA
Checkout, SVA Unload
DIB CASA SVA, Bill Payment, POS Payment, Remittance, Checkout
SVA (Cash Advance), Remittance (Cash Advance), POS Payment,
DIB Credit Card
Checkout
SVA (Cash Advance), Remittance (Cash Advance), POS Payment,
Other Cards
Checkout
Cash in CCDM / Agent SVA

Chart of Accounts

The different accounts involved during the accounting processes are mentioned in the below table:

Account Name Description

Customer SVA Account The subscriber’s SVA account
Customer Account (Individual) The subscriber’s CASA account
PinPay Wallet Platform Intraday Pool PinPay’s Wallet’s Platform suspense account at DIB
(Individual)
Wallet PlatformPinPay Pool in DIB Wallet PlatformPinPay’s shadow pool account at DIB
(Consolidated Debit/Credit)
CC More Cash (Individual) Subscriber’s Credit Card account at DIB
Walaa More Cash (Individual) Subscriber’s Walaa account at DIB
Biller Account (Individual Transaction) Biller’s account at DIB
ATM Cash Account ATM account at DIB
ATM pool account at DIB for Remit2ATM Wallet PlatformPinPay
Remit2ATM Wallet PlatformPinPay Pool
transactions
DIB Commission P/L P/L account at DIB for commissions and fees

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 46 of 252
 Dubai Islamic Bank-IT Department

Recon/Settlement Files

When Wallet PlatformPinPay notifies DIB bank of the different transactions that occurred, Wallet PlatformPinPay will
submit a batch file that includes a number of files related to the payments which were conducted during the day.

The different files are mentioned in the table below:

Transaction Type File Types Debit Credit

Remittance Principle Remittance Principle Settlement (Recon) Consolidated Individual
Remit 2 ATM Remit2ATM Principle Settlement (Recon) Consolidated Individual
Cash in through CCDM CCDM Principle Settlement (Recon) Individual Consolidated
Bill Payment through CASA CASA Transfer Principle Settlement (Recon) Individual Consolidated
Bill Payment through Credit Credit Card Transfer Principle Settlement Individual Consolidated
Card (Recon)
Wala’a Transfer Principle Settlement Individual Consolidated
Bill Payment through Walaa
(Recon)
Biller and Customer Settlement Individual Individual
(Settlement) – includes:
 Biller
Settlement File
 Reversals
 Unload Settlements
 Fees

Biller Notification File

At the end of every business day, Wallet PlatformPinPay will be generating a Biller Notification file that will include the
transaction details of all bill payments conducted during the day.

Wallet PlatformPinPay will be sending these files directly to the billers.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 47 of 252
 Dubai Islamic Bank-IT Department

CASA

When a subscriber conducts a transaction through his CASA account, the total bill amount including the related fees
are debited from the subscriber’s CASA account and moved to the PinPay Wallet Platform Intraday Pool Account at
DIB. The total amount is later moved to the Wallet PlatformPinPay Pool account at DIB for settlement with the billers.

The workflows covered in this section will include the following:

 Bill Payment – Online
 File Upload Payment
 Blind Payment

Workflow

Step 1
Subscriber initiates a bill payment transaction using his PinPay Wallet app.

Step 2
The request is sent to the Wallet Platform PinPay system for validation and processing. After processing the
transaction, the request is forwarded to the DIB system through the Member Center.

Step 3
The DIB system receives the bill payment request and performs a hold on the subscriber’s account for the funds. The
exact timing to release the hold in case Wallet PlatformPinPay does not send the claim will be discussed with DIB and
same need to be configurable. Unsuccessful transactions are put on hold for a period of three days (expiry period). The
hold will automatically be released in three days if the Mobile Wallet system does not send a settlement file with the
reversal request.

Step 4
The DIB system returns the operation result back to PinPay Wallet Platform through the Member Center. Wallet
PlatformPinPay notifies the subscriber of the payment via email.

Step 5
At the end of day, the Wallet PinPay systemPlatform will send DIB a settlement file that contains a list of transactions
that occurred during the day:

 CASA Transfer Principle Settlement (Recon)

 Settlement File

DIB will then perform the following accounting activities:

From subscriber’s account at DIB to Wallet PlatformPinPay Intraday Pool Account:

Account Debit Credit
[Customer Account] 115 AED
[Wallet PlatformPinPay Intraday 115 AED
Pool Account]

From Intraday Account to Wallet SVA Pool Account:

Account Debit Credit
ITPMO-INI-002 Version 1.2, June 2015
Controlled Document For Internal Use Only Page 48 of 252
 Dubai Islamic Bank-IT Department

[Wallet PlatformPinPay Intraday 115 AED

Pool Account]
[Wallet PlatformPinPay Pool in DIB] 115 AED

Settlement from Wallet SVA Pool Account to Biller Account:

Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 100 AED
[Biller Account] 100 AED

Commission Settlement from Wallet SVA Account to P/L Account – fees include both Sender and Receiver fees
Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 15 AED
[DIB Commission P/L] 15 AED

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 49 of 252
 Dubai Islamic Bank-IT Department

Figure 8 - Bill Payment (CASA) Figure 17 - Bill Payment CASA (online bill)

Bill Payment Accounting Flow – CASA (Online Bill Payment) Field Code Changed

Subscriber Wallet System Member Center DIB

Initiate Bill Payment

Receive Bill
Transaction from DIB 1
Inquiry Request
Wallet

Sends Bill Receives Bill

Bill Inquired Receives Bill  Holds transaction amount
3 4 Payment 5 Payment
from Biller Details
request to DIB request

6
Processes
Payment & Returns operation
Send response
Subscriber Notifies receives result and
10 9 8 back to Wallet 7
notified subscriber Confirmation Authorization
System
Request from Message
Biller

Releases Hold and Posts:

End of Day: Forwards Receives  Debits [Customer Account]
Sends Settlement File 11 settlement 12 Settlement
and Claim File (for CASA) file File  Credits [Wallet Platform
Intraday Pool]

 Debits [Wallet Platform

Intraday Pool]

 Credits [Wallet Platform Pool

in DIB]

For Amount:
 Debits [Wallet Platform Pool
in DIB]

 Credits [Biller Account]

For Fees:
 Debits [Wallet Platform Pool
in DIB] for fees
End of Day

 Credits [DIB Commission P/L]

for fees
 Dubai Islamic Bank-IT Department

Figure 28 - Bill Payment (CASA) - File Upload

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 51 of 252
 Dubai Islamic Bank-IT Department

Bill Payment Accounting Flow – CASA (File Upload) Field Code Changed

Subscriber Wallet System Member Center DIB

Formatted: Font: 11 pt, Not Bold, Font color: Auto

Initiate Bill Payment

Receive Bill
Transaction from DIB 1
Inquiry Request
Wallet

Bill Inquired Sends Bill Receives Bill

Receives Bill  Holds transaction amount
from Wallet 3 4 Payment 5 Payment
Details
System request to DIB request

Returns operation
Send response
Subscriber Notifies Processes result and
10 9 8 back to Wallet 7
notified subscriber Payment Authorization
System
Message

End of Day:
Sends Biller Transaction
File & Receives Biller
Confirmation Message

11
Releases Hold and Posts:
End of Day: Forwards Receives  Debits [Customer Account]
Sends Settlement File 12 settlement 13 Settlement
and Claim File (for CASA) file File  Credits [Wallet Platform
Intraday Pool]

 Debits [Wallet Platform

Intraday Pool]

 Credits [Wallet Platform Pool

in DIB]

For Amount:
 Debits [Wallet Platform Pool
in DIB]

 Credits [Biller Account]

For Fees:
 Debits [Wallet Platform Pool
in DIB] for fees
End of Day

 Credits [DIB Commission P/L]

for fees

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 52 of 252
 Dubai Islamic Bank-IT Department

Figure 39 - Bill Payment (CASA) – Blind

Bill Payment Accounting Flow – CASA (Blind Payment) Field Code Changed

Subscriber Wallet System Member Center DIB

Initiate Bill Payment Receive Bill

Transaction from 1 Payment
PinPay App Request

Receives
Transaction Sends Payment  Holds transaction amount
3 5 Payment
Validated request to DIB
request

6
Processes
Returns operation
Payment & Send response
Subscriber Notifies result and
10 9 sends Biller 8 back to Wallet 7
notified subscriber Authorization
Notification System
Message
Message

Releases Hold and Posts:

End of Day: Forwards Receives  Debits [Customer Account]
Sends Settlement File 12 settlement 13 Settlement
and Claim File (for CASA) file File  Credits [Wallet Platform
Intraday Pool]

 Debits [Wallet Platform

Intraday Pool]

 Credits [Wallet Platform Pool

in DIB]

For Amount:
 Debits [Wallet Platform Pool
in DIB]

 Credits [Biller Account]

For Fees:
 Debits [Wallet Platform in
DIB] for fees

 Credits [DIB Commission P/L]

End of Day

for fees

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 53 of 252
 Dubai Islamic Bank-IT Department

Bill Payment Accounting Flow - CASA

Subscriber PinPay System Member Center DIB

Initiate Bill Payment Receive Bill

Transaction from 1 Payment
PinPay App Request

Sends Bill Receives Bill

Processes  Holds transaction amount
3 Payment 4 Payment
Transaction
request to DIB request

Returns
Subscriber Notifies Send response
8 7 6 operation
notified subscriber back to PinPay
result

Releases Hold and Posts:

End of Day: Forwards Receives  Debits [Customer Account]
Sends 11 settlement 12 Settlement
Settlement File file File  Credits [PinPay Intraday Pool]

 Debits [PinPay Intraday Pool]

 Credits [PinPay Pool in DIB]

For Amount:
 Debits [PinPay Pool in DIB]

 Credits [Biller Account]

For Fees:
 Debits [PinPay Pool in DIB] for
fees

ITPMO-INI-002 Version 1.2, June

P/L]2015
End of Day

 Credits [DIB Commission

Controlled Document For Internal Use Only for fees Page 54 of 252
 Dubai Islamic Bank-IT Department

Credit Card

The total bill amount including the related fees are debited from the subscriber’s Credit Card account and moved to
the Wallet PlatformPinPay Intraday Pool Account at DIB. The total amount is later moved to the Wallet PlatformPinPay
Pool account at DIB for settlement with the billers.

Workflow

Step 1
Subscriber initiates a bill payment transaction using his PinPay Wallet app.

Step 2
The request is sent to the PinPay systemWallet Platform for validation and processing. After processing the
transaction, the request is forwarded to the DIB system through the Member Center.

Step 3
The DIB system receives the bill payment request and performs a hold on the subscriber’s account for the funds. The
exact timing to release the hold in case Wallet PlatformPinPay does not send the claim will be discussed with DIB.

Step 4
The DIB system returns the operation result back to PinPay through the Member Center. Wallet PlatformPinPay
notifies the subscriber of the payment via email.

Step 5
At the end of day, the PinPay systemWallet Platform will send DIB a settlement file that contains a list of transactions
that occurred during the day:

 Credit Card Transfer Principle Settlement (Recon)

 Settlement File

DIB will then perform the following accounting activities:

From subscriber’s Credit Card account at DIB to Wallet PlatformPinPay Intraday Pool Account:
Account Debit Credit
[CC More Cash] 115 AED
[Wallet PlatformPinPay Intraday 115 AED
Pool Account]

From Intraday Account to Wallet SVA Pool Account:

Account Debit Credit
[Wallet PlatformPinPay Intraday 115 AED
Pool Account]
[Wallet PlatformPinPay Pool in DIB] 115 AED

Settlement from Wallet SVA Pool Account to Biller Account:

Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 100 AED
[Biller Account] 100 AED

Commission Settlement from Wallet SVA Account to P/L Account – fees include both Sender and Receiver fees
Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 15 AED
[DIB Commission P/L] 15 AED
 Dubai Islamic Bank-IT Department

Figure 9 - Bill Payment (Credit Card)

Figure 410 - Bill Payment (Credit Card) Formatted: Caption

 Dubai Islamic Bank-IT Department

Field Code Changed

Bill Payment Accounting Flow – Credit Card

Subscriber Wallet Platform Member Center DIB

Initiate Bill Payment Receive Bill

Transaction from DIB 1 Payment
Wallet Request

2
Processes
Payment & Sends Bill Receives Bill
Transaction  Holds transaction amount
3 sends Biller 4 Payment 5 Payment
Validated
Notification request to DIB request
Message
6

Send response Returns operation

Subscriber Notifies
9 8 back to Wallet 7 result and
notified subscriber
Platform Authorization
Message

 Debits [CCMore Cash]

End of Day: Forwards Receives
Sends Settlement File 10 settlement 11 Settlement  Credits [Wallet Platform
and Claim File (for CASA) file File Intraday Pool Account]

 Debits [Wallet Platform

Intraday Pool Account]

 Credits [Wallet Platform Pool

in DIB]

For Amount:
 Debits [Wallet Platform Pool
in DIB]

 Credits [Biller Account]

For Fees:
 Debits [Wallet Platform Pool
in DIB] for fees

 Credits [DIB Commission P/L]

ITPMO-INI-002 Version 1.2, June 2015
for fees
Controlled Document For Internal Use Only Page 57 of 252
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 58 of 252
 Dubai Islamic Bank-IT Department

Bill Payment Accounting Flow – Credit Card

Subscriber PinPay System Member Center DIB

Initiate Bill Payment Receive Bill

Transaction from 1 Payment
PinPay App Request

Sends Bill Receives Bill

Processes  Holds transaction amount
3 Payment 4 Payment
Transaction
request to DIB request

Returns
Subscriber Notifies Send response
8 7 6 operation
notified subscriber back to PinPay
result

 Debits [CCMore Cash]

Forwards Receives
Sends
9 settlement 10 Settlement  Credits [PinPay Intraday Pool
Settlement File
file File Account]

 Debits [PinPay Intraday Pool

Account]

 Credits [PinPay Pool in DIB]

For Amount:
 Debits [PinPay Pool in DIB]

 Credits [Biller Account]

For Fees:
 Debits [PinPay Pool in DIB] for
fees

 Credits [DIB Commission P/L]

for fees
ITPMO-INI-002 Version 1.2, June 2015
Controlled Document For Internal Use Only Page 59 of 252
 Dubai Islamic Bank-IT Department

Hold Functionality

 The hold functionality should be a minimum of 3 days, in case the resolution time with the biller takes time
 Dubai Islamic Bank-IT Department

Wallet SVA

The total bill amount including the related fees are debited from the Wallet PlatformPinPay Pool Account at DIB. The
total amount is later settled with the billers from the Wallet PlatformPinPay Pool Account.

Workflow

Step 1
Subscriber initiates a bill payment transaction using his PinPay Wallet app.

Step 2
The request is sent to the PinPay systemWallet Platform for validation and processing.

Step 3
After processing the transactions, Wallet PlatformPinPay notifies the subscriber of the successful payment via Email.

Step 4
At the end of day, the PinPay systemWallet Platform will send DIB a settlement file that contains a list of transactions
that occurred during the day. DIB will then perform the following accounting activities:

Settlement from Wallet SVA Pool Account to Biller Account & Commission Settlement from Wallet SVA Account to P/L
Account – fees include both Sender and Receiver fees:

Account Debit Credit

[Wallet PlatformPinPay Pool in DIB] 115 AED
[Biller Account] 100 AED
[DIB Commission P/L] 15 AED

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 61 of 252
 Dubai Islamic Bank-IT Department

Figure 511 - Bill Payments (Wallet SVA) Figure 10 - Bill Payments (Wallet SVA)

Field Code Changed

Bill Payment Accounting Flow – Wallet SVA

Subscriber Wallet Platform Member Center DIB

Initiate Bill Payment Receive Bill

Transaction from DIB 1 Payment
Wallet Request

Processes
Transaction

Subscriber Notifies
8
notified subscriber

For Amount:
Forwards Receives  Debits [Wallet Platform Pool
Sends
4 settlement 5 Settlement in DIB]
Settlement File
file File
 Credits [Biller Account]

For Fees:
 Debits [Wallet Platform Pool
in DIB] for fees

 Credits [DIB Commission P/L]

for fees
 Dubai Islamic Bank-IT Department

Bill Payment Accounting Flow – Wallet SVA

Subscriber PinPay System Member Center DIB

Initiate Bill Payment Receive Bill

Transaction from 1 Payment
PinPay App Request

Processes
Transaction

Subscriber Notifies
8
notified subscriber

For Amount:
Forwards Receives  Debits [PinPay Pool in DIB]
Sends
4 settlement 5 Settlement
Settlement File
file File  Credits [Biller Account]

For Fees:
 Debits [PinPay Pool in DIB] for
fees

 Credits [DIB Commission P/L]

for fees

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 63 of 252
 Dubai Islamic Bank-IT Department

Figure 11 - Bill Payment (Wallet SVA)

Formatted: Font: 11 pt, Not Bold, Italic

Formatted: Normal

Exception Management

This section will cover the exception management process that could occur during a bill payment transaction when
the subscriber’s uses his CASA account.

Biller Service Not Rendered – CASA/Credit Card

There are a number of issues that could occur during a bill payment transaction that could result in a failure to provide
the biller service to the subscriber.

When a payment has failed and the biller service is not rendered, Wallet PlatformPinPay is immediately alerted of the
issue. Based on this alert notification and after further investigation in the system, Wallet PlatformPinPay is 100%
certain that the service has failed and the subscriber did not receive the biller service purchased (whether it was a bill
payment, voucher purchase etc.)

In this case, Wallet PlatformPinPay would have to either reverse or refund the transaction back to the subscriber.

A. Reversal

A reversal transaction occurs when the payment is unsuccessful, rendering the transaction process incomplete.

When the transaction is conducted by the subscriber, the funds at the subscriber’s CASA or Credit Card account are
held by DIB. The PinPay systemWallet Platform is alerted that the transaction has failed since the biller service itself
was not rendered. During this situation, the payment would need to be reversed.

Considering there will be an expiry period to release the hold, Wallet PlatformPinPay will not be required to send a
claim file (reversal file). The amount will be reversed after the expiry period – need to discuss this option more with
DIB to finalize the reversal process. If this process is followed, Wallet PlatformPinPay will maintain an audit log of the
failures.

In the option that there is no hold, Wallet PlatformPinPay would then send DIB a reversal file (Settlement File) at the
end of the day, notifying the bank of the reversal that needs to be done. There is no automatic reversal.

In this case DIB would release the funds that were held and the customer’s account (CASA or Credit Card) would not
be debited.
 Dubai Islamic Bank-IT Department

B. Refund

A refund transaction occurs when a dispute is raised by the subscriber. The subscriber may raise a dispute when the
biller service was not rendered, but the payment amount including fees has already been debited from his account
and posted to the biller’s account and the DIB Commission P/L account.

After the transaction has already been posted, Wallet Platform PinPay would notify the bank that the payment
would need to be refunded. This refund request is only submitted the following day after Wallet PlatformPinPay has
100% confirmation that the service has failed to be delivered to the subscriber.

Initial Posting
When the transaction is conducted, DIB will debit the subscriber’s CASA account and credit the Wallet
PlatformPinPay Intraday Pool Account.

Account Debit Credit

[Customer Account] 115 AED
[Wallet PlatformPinPay Intraday 115 AED
Pool Account]

DIB will notify Wallet PlatformPinPay of the operation and Wallet PlatformPinPay will send DIB a settlement file at
the end of the day with the transactions conducted. DIB will then conduct the following accounting activities:

Account Debit Credit

[Wallet PlatformPinPay Intraday 115 AED
Pool Account]
[Wallet PlatformPinPay Pool in DIB] 115 AED

Settlement from Wallet PlatformPinPay Pool Account to Biller Account:

Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 100 AED
[Biller Account] 100 AED

Commission Settlement from Wallet SVA Account to P/L Account – fees include both Sender and Receiver fees
Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 15 AED
[DIB Commission P/L] 15 AED

Settlement File - Refund

After further investigation and Wallet PlatformPinPay confirms that the biller service was not rendered, Wallet
PlatformPinPay will send another settlement file to DIB the following day to notify the bank of the required refund.

Total amount excluding the related fees are refunded back to the subscriber’s CASA account:
Account Debit Credit
[Biller Account] 100 AED
[Customer Account] 100 AED

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 65 of 252
 Dubai Islamic Bank-IT Department

The related fees are refunded back to the subscriber’s CASA account:
Account Debit Credit
[DIB Commission P/L] 15 AED
[Customer Account] 15 AED

Note that the above process also applies to Credit Card.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 66 of 252
 Dubai Islamic Bank-IT Department

Third Party Accounts

The third party account process will have its own pool account. At the end of the day, the Mobile Wallet System will
send DIB a settlement file with the entries.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 67 of 252
 Dubai Islamic Bank-IT Department

5.2. Fund / Un-Fund Wallet SVA

Subscribers will be able to fund their Wallet SVA accounts in order to conduct transactions using their Wallet SVA
account type.

This section will cover the following Wallet SVA functions that can be performed by the subscriber:

 Funding the Wallet SVA

 Un-funding the Wallet SVA – will eventually remove this option on the app level
 Closing the Wallet SVA – will eventually add this option on the app level

Fund

Subscribers can only fund their Wallet SVA’s from their CASA accounts and credit card.

The funding process starts by debiting the subscriber’s CASA account at DIB, then crediting the Wallet SVA with the
corresponding amount. The PinPay systemWallet Platform then notifies DIB and the subscriber of the Wallet SVA fund
transaction.

The PinPay systemWallet Platform initiates the Fund Wallet SVA process.

Workflow

Step 1
The subscriber requests to fund his Wallet SVA. The Wallet PlatformPinPay Wallet System sends a request to DIB
through the Member Center with the required information including how much to fund.

Step 2
DIB then does the following account activities:

From subscriber’s account at DIB to Wallet PlatformPinPay Intraday Pool Account:

The DIB system receives the fund request and performs a hold on the subscriber’s account for the amount. The exact
timing to release the hold in case Wallet PlatformPinPay does not send the claim will be discussed with DIB.

DIB returns a fund confirmation response to the PinPay SystemWallet Platform via the Member Center.

Step 3
The PinPay SystemWallet Platform then funds the subscriber’s Wallet SVA with the corresponding amount, before
notifying DIB of the balance change.

Step 4
At the end of day, the PinPay systemWallet Platform will send DIB a settlement file that contains a list of transactions
that occurred during the day. DIB will then perform the following accounting activities:

From subscriber’s account at DIB to Wallet PlatformPinPay Intraday Pool Account (hold released):

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 68 of 252
 Dubai Islamic Bank-IT Department

Account Debit Credit

[Customer Account] 100 AED
[Wallet PlatformPinPay Pool 100 AED
Account]

Commission Settlement from Wallet PlatformPinPay Pool Account to DIB Commission P/L - Wallet PlatformPinPay will
handle the accounting entries for the funding of the wallet if there are any fees.

If funding is done through the credit card, the card system takes care of the fees.

Account Debit Credit

[Wallet PlatformPinPay Pool 15 AED
Account]
[DIB Commission P/L] 15 AED

The Wallet SVA balance will automatically refresh itself after the funding is successful.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 69 of 252
 Dubai Islamic Bank-IT Department

Figure 612 - Fund Wallet SVA Figure 12 - Fund Wallet SVA Workflow

Field Code Changed

Fund Wallet SVA – From Wallet System to DIB

Subscriber Wallet Platform Member Center DIB System

Receive Fund Send Fund Sends Fund

Initiate Fund Wallet Receive Fund
1 Wallet SVA 2 Request to 3 Wallet SVA 4  Holds funds
SVA Request Request
Request Member Center request to DIB

 Perform Checks and

Validations

Fund Wallet Return Fund

Receive Fund 5
SVA with 7 6 Operation
Confirmation
funds Result
8 8

Notify Queue for  Debits [Customer Account]

Receive Fund Wallet Notify Receives
Member 9 Notification 10 11  Credits [Wallet Platform Pool
SVA Notification Subscriber Batch File
Center Batch File in DIB]

 Debits [Wallet Platform Pool

in DIB]
 Credits [DIB Commission P/L]
 Dubai Islamic Bank-IT Department

Fund Wallet SVA – From PinPay Wallet System to DIB

Subscriber PinPay Wallet System Member Center DIB System

Receive Fund Send Fund Sends Fund

Initiate Fund Wallet Receive Fund
1 Wallet SVA 2 Request to 3 Wallet SVA 4  Holds funds
SVA Request Request
Request Member Center request to DIB

 Perform Checks and

Validations

Fund Wallet Return Fund

Receive Fund 5
SVA with 7 6 Operation
Confirmation
funds Result
8 8

Notify Queue for  Debits [Customer Account]

Receive Fund Wallet Notify Receives
Member 9 Notification 10 11  Credits [PinPay Pool in DIB]
SVA Notification Subscriber Batch File
Center Batch File

 Debits [PinPay Pool in DIB]

 Credits [DIB Commission P/L]

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 71 of 252
 Dubai Islamic Bank-IT Department

Un-Fund

Subscribers can un-fund their Wallet SVA’s to their CASA accounts.

When a un-fund transaction is initiated by the subscriber, the request is logged at the Bank Portal queue for a DIB
bank user to review and approve/reject. If approved, the transaction will be included in the settlement file.

Note that this transaction has a fee applied to it.

The PinPay systemWallet Platform initiates the Un-Fund Wallet SVA process.

Workflow

Step 1
The subscriber requests to un-fund his Wallet SVA. The Wallet PlatformPinPay Wallet System sends a request to DIB
through the Member Center with the required information including how much to un-fund.

Step 2
The request is logged in the Bank Portal (back-office) for a DIB bank user (authorizer) to review. He can then approve
or reject the request.

If approved, DIB then does the following account activities:

From subscriber’s account at DIB to Wallet PlatformPinPay Intraday Pool Account:

Account Debit Credit

[Wallet PlatformPinPay Pool 100 AED
Account]
[Customer Account] 100 AED

DIB returns ana un-fund confirmation response to the PinPay SystemWallet Platform via the Member Center.

Step 3
The PinPay SystemWallet Platform then un-funds the subscriber’s Wallet SVA with the corresponding amount, before
notifying DIB of the balance change.

Step 4
At the end of day, the PinPay systemWallet Platform will send DIB a settlement file that contains a list of transactions
that occurred during the day. DIB will then perform the following accounting activities:

Commission Settlement from Wallet PlatformPinPay Pool Account to DIB Commission P/L:

Account Debit Credit

[Wallet PlatformPinPay Pool 15 AED
Account]
[DIB Commission P/L] 15 AED

Step 5
Subscriber is notified that his un-fund request was successful.
 Dubai Islamic Bank-IT Department

Figure 13 - Un-fund Wallet SVA Workflow Figure 713 - Unfund Wallet SVA

Field Code Changed

Un-Fund SVA Wallet – From Wallet System to DIB

Subscriber Wallet Platform Member Center DIB System

Receive SVA Send Un-Fund

Initiate Un-Fund SVA Send Un-Fund Receive Un-
1 Wallet Un-Fund 2 Request to 3 4
Wallet Request Request to DIB Fund Request
Request Member Center
5

An authorizer
 Perform Checks and will approve/
Validations reject it
6

Approves
Un-Fund Wallet SVA Receive Un- Send Un-Fund
request.
with corresponding 9 Fund 8 Request to 7
Return Un-
amount Confirmation Wallet Platform
Fund
10 Operation
Result
 Debits [Wallet Platform Pool
in DIB]
Notify Queue for 13  Credits [Customer Account]
Receive Wallet SVA Receives
Notify Bank Member 11 Notification 12
Un-Fund Notification Batch File
Center Batch File
 Debits [Wallet Platform Pool
in DIB]
 Credits [DIB Commission P/L]
 Dubai Islamic Bank-IT Department

Un-Fund SVA Wallet – From PinPay System to DIB

Subscriber PinPay Wallet system Member Center DIB System

Receive SVA Send Un-Fund

Initiate Un-Fund SVA Send Un-Fund Receive Un-
1 Wallet Un-Fund 2 Request to 3 4
Wallet Request Request to DIB Fund Request
Request Member Center
5

An authorizer
 Perform Checks and will approve/
Validations reject it
6

Approves
Un-Fund Wallet SVA Receive Un- Send Un-Fund
request.
with corresponding 9 Fund 8 Request to 7
Return Un-
amount Confirmation PinPay
Fund
10 Operation
Result
 Debits [PinPay Pool in DIB]
 Credits [Customer Account]
Notify Queue for 13
Receive Wallet SVA Receives
Notify Bank Member 11 Notification 12
Un-Fund Notification Batch File
Center Batch File
 Debits [PinPay Pool in DIB]
 Credits [DIB Commission P/L]

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 74 of 252
 Dubai Islamic Bank-IT Department

Closing

Subscribers can close their Wallet SVA accounts.

It starts by initially blocking the subscriber’s Wallet SVA so that it becomes inactive and non-operational. The PinPay
systemWallet Platform then un-funds the subscriber’s Wallet SVA so that the balance is 0. On DIB’s end, the funds are
unloaded to the subscriber’s CASA account.

The PinPay systemWallet Platform then closes the Wallet SVA and sends a notification to DIB and subscriber of the
Wallet SVA closure.

The PinPay systemWallet Platform initiates the close Wallet SVA process.

Workflow

Step 1
The subscriber requests to close his Wallet SVA. The Wallet PlatformPinPay Wallet System receives the close Wallet
SVA request and initially blocks the subscriber’s Wallet SVA.

Step 2
The PinPay systemWallet Platform then sends DIB an un-funding request through the Member Center (please refer to
un-funding process flow section for more info).

Step 3
The PinPay systemWallet Platform receives DIB’s response and proceeds to un-fund the Wallet SVA balance to 0 on its
end. Afterwards, the PinPay systemWallet Platform then closes the Wallet SVA and notifies both the subscriber and
DIB of the changes.
 Dubai Islamic Bank-IT Department

Figure 14 - Closing Wallet SVA Workflow Figure 814 - Closing Wallet SVA

Field Code Changed

Close Wallet SVA – From Wallet System to DIB

Subscriber Wallet Platform Member Center DIB

Send Un-Fund
Initiate Close Wallet SVA Receive Close Wallet Blocks subscriber s Send Un-Fund Conducts required un-fund
1 2 3 Request to Member 4 5
Request SVA Request Wallet SVA Request to DIB Wallet SVA processes
Center

 Perform Necessary
Checks and
Validations
6

Sends Unload Operation

Receive Unload Operation Return Un-Fund
Closes Wallet SVA 10 Un-Fund Wallet SVA 9 8 Confirmation to Wallet 7
Confirmation Operation Result
Platform

11

Receive Close Wallet SVA Receive Close Wallet SVA

Notification Notify Customer Notify Member Center 12 Notify DIB 13 Confirmation from Wallet
Platform
 Dubai Islamic Bank-IT Department

Close Wallet SVA – From PinPay Wallet System to DIB

Subscriber PinPay Wallet System Member Center DIB

Send Un-Fund
Initiate Close Wallet SVA Receive Close Wallet Blocks subscriber s Send Un-Fund Conducts required un-fund
1 2 3 Request to Member 4 5
Request SVA Request Wallet SVA Request to DIB Wallet SVA processes
Center

 Perform Necessary
Checks and
Validations
6

Receive Unload Operation Sends Unload Operation Return Un-Fund

Closes Wallet SVA 10 Un-Fund Wallet SVA 9 8 7
Confirmation Confirmation to PinPay Operation Result

11

Receive Close Wallet SVA Receive Close Wallet SVA

Notification Notify Customer Notify Member Center 12 Notify DIB 13 Confirmation from PinPay
Wallet System

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 77 of 252
 Dubai Islamic Bank-IT Department

6.3. P2P
All money transfer operations (including sending and receiving money) will be conducted using the subscriber’s Wallet
SVA. The subscriber will not be able to transfer any funds using any of his other linked account types, such as his CASA,
Loyalty and Credit Card etc.

Therefore, both the sender and recipient of a P2P transaction must have Wallet SVA’s created in the system in order
for the transfer to be executed successfully.

There are two different workflows that will be documented in this section:

 P2P without transfer Fees

 P2P with transfer Fees

P2P – Without Transfer Fees Workflow

Step 1
Senders initiates a money transfer transaction. He is informed on the app of the successful transfer. The recipient
receives a notification in-app and via SMS that money has been sent to his SVA account.

For money transfers conducted without any transfer fees, Wallet PlatformPinPay initially checks with the bank on the
receiver’s account status – it checks on whether it is active or inactive.

Step 2
Once Wallet PlatformPinPay receives confirmation on the receiver’s account, the funds are instantly debited from the
sender’s Wallet SVA account and credited into the recipient’s Wallet SVA account.

Both Wallet SVA’s are located in the PinPay systemWallet Platform and no requests are sent to the Member Center or
DIB.

The Wallet PlatformPinPay Pool account located at DIB is not touched in this scenario, since the funds located at the
shadow pool account remain the same.

When the recipient accepts the money, both subscribers are notified of the transfer via SMS.
 Dubai Islamic Bank-IT Department

Figure 15 - P2P without Fees Figure 915 - P2P Without Fees

Field Code Changed

P2P – Without Fees

Subscriber Wallet Platform Member Center DIB System

Sends request to DIB

Initiate P2P Request 1 Receive P2P Request 2 3 Checks recipient s account
System

 Debit Sender s Wallet SVA

 Credit Recipient s Wallet SVA 5 Returns operation result 4

Receive P2P
7 Notify Subscriber
Notification
 Dubai Islamic Bank-IT Department

P2P – Without Fees

Subscriber PinPay Wallet System Member Center DIB System

Sends request to DIB

Initiate P2P Request 1 Receive P2P Request 2 3 Checks recipient s account
System

 Debit Sender s Wallet SVA

 Credit Recipient s Wallet SVA 5 Returns operation result 4

Receive P2P
7 Notify Subscriber
Notification

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 80 of 252
 Dubai Islamic Bank-IT Department

P2P – With Transfer Fees Workflow

If a money transfer is conducted with transfer fees, the Wallet PlatformPinPay Pool account at DIB must be adjusted
to accommodate the amount and fees included in the transaction.

Step 1
Senders initiates a money transfer transaction. He is informed on the app of the successful transfer. The recipient
receives a notification in-app and via SMS that money has been sent to his SVA account.

When the transfer is initiated, the PinPay systemWallet Platform will debit the sender’s Wallet SVA account and credit
the recipient’s Wallet SVA account. For the fees:

 For fees collected from the sender: The money sent will be the full amount minus the fees
 For fees collected from the recipient: The money received will be the full amount minus the fees.

Step 2
When the recipient accepts the money, both subscribers are notified of the transfer via SMS.

Step 3
The PinPay systemWallet Platform will then send DIB (through the Member Center) a batch file that includes the
amount transferred with the fees, at the end of the day. DIB will then update its accounts in the following way:

Commission Settlement from Wallet PlatformPinPay Pool Account to DIB Commission P/L:

Account Debit Credit

[Wallet PlatformPinPay Pool 15 AED
Account]
[DIB Commission P/L] 15 AED

Note the following notifications that the subscriber may receive via SMS and in-app notifications:
 Money sent
 Incoming Pending
 Outgoing Pending
 Outgoing Expired
 Incoming Execution Fail
 Outgoing Execution Fail
 Incoming Rejected
 Outgoing Rejected
 Incoming Accepted
 Incoming Expired
 P2P Incoming Pending (No profile)
 Dubai Islamic Bank-IT Department

Figure 16 - P2P with Fees Figure 1016 - P2P With Fees

 Dubai Islamic Bank-IT Department

Field Code Changed

P2P – With Fees

Subscriber Wallet Platform Member Center DIB System

Sends request to Member

Initiate P2P Request 1 Receive P2P Request 2 3 Sends request to DIB 4 Updates accounts
Center

 Debit Sender s Wallet SVA Receive confirmation  Debits [Customer Account]

 Credit Receiver s Wallet SVA 8 7 Return operation result 6  Credits [Wallet Platform Pool
result
Account]

 Debits [Wallet Platform Pool

Receive P2P Sends notification to Account]
10  Credits [DIB Commission P/L]
Notification subscriber

14
11

Sends Batch File to Receive P2P Notification

12 Sends Batch File to DIB 13
Member Center from Member Center

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 83 of 252
 Dubai Islamic Bank-IT Department

P2P – With Fees

Subscriber PinPay Wallet System Member Center DIB System

Sends request to Member

Initiate P2P Request 1 Receive P2P Request 2 3 Sends request to DIB 4 Updates accounts
Center

 Debit Sender s Wallet SVA Receive confirmation  Debits [Customer Account]

 Credit Receiver s Wallet SVA 8 7 Return operation result 6  Credits [PinPay Pool Account]
result

Receive P2P Sends notification to  Debits [PinPay Pool Account]

Notification
10
subscriber  Credits [DIB Commission P/L]

11 14

Sends Batch File to Receive P2P Notification

12 Sends Batch File to DIB 13
Member Center from Member Center

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 84 of 252
 85

7.4. Remit to ATM

The Remit to ATM transaction will enable subscribers to cash out funds at DIB ATMs. When withdrawing money, the
subscriber will withdraw funds from the Wallet SVA of the sender.

This process requires the beneficiary to enter a secret code (Token) received via SMS into the ATM in order to receive
the money.

During settlement, if there are any transactions that were not knocked off, reversals will be made. The settlement file
will only include transactions that were confirmed withdrawals from the ATM (DIB has sent its confirmation to Wallet
PlatformPinPay).

Workflow

Step 1
The subscriber must initially select the Remit to ATM function available on the Wallet PlatformPinPay app. The
subscriber then enters the amount (add notes or remarks field here) he wishes to withdraw from his Wallet SVA,
before submitting his request by entering his M-PIN.

Step 2
Wallet PlatformPinPay receives the request and forwards it to DIB via the Member Center.

Step 3
The Member Center then performs the following accounting activities (holds the amounts). The amounts are held on
Wallet PlatformPinPay’s end, the following accounts are updated on Wallet PlatformPinPay’s end:

Debits the Wallet PlatformPinPay Pool in DIB account and Remit2ATM Pool Wallet PlatformPinPay account with total
amount:
Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 100 AED
[Remit2ATM Pool PinPay] 100 AED

Debit’s the PinPay Pool in DIB account and Credits the P/L account with the fees:
Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 15 AED
[Commission P/L] 15 AED

Step 4
The Member Center then forwards the request to DIB for authentication. Afterwards, DIB generates a Token and sends
it to the beneficiary via SMS.

The beneficiary must enter the Token into the ATM in order to withdraw the money.

Step 5
At the end of the day, Wallet PlatformPinPay will be sending DIB a batch file (Remit2ATM Principle Settlement – Recon)
that includes all the transactions conducted. DIB will then update the appropriate accounts on its end:

Accounts updated on DIB’s end:

Account Debit Credit
[Wallet PlatformPinPay Pool in DIB] 100 AED
[Remit2ATM Pool PinPay] 100 AED
 Dubai Islamic Bank-IT Department

Account Debit Credit

[Remit2ATM Wallet Platform PinPay 100 AED
Pool Account]
[ATM Cash Account] 100 AED

Step 6
The subscriber will receive an SMS notifying of the successful ATM withdrawal.

Note the following notifications that the subscriber may receive via SMS:
 Successful Payment
 Failed Payment General Error
 Failed Payment – Invalid OTP
 Failed Payment – Invalid Mobile Number entered
 Failed Payment – Insufficient Funds
 Failed Payment – Limit Reached
 Failed Payment – Payment reversed successfully

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 86 of 252
 87

Figure 17 - Remit to ATM Figure 1117 - Remit to ATM

Field Code Changed

Remit to ATM – Request Token

Subscriber DIB Wallet Wallet Platform Member Center DIB System

Initiate Remit to Enters Amount Receives Remit Forwards Processes

1 2 3. Forward to Member Center 4
ATM request to Remit to ATM request request to DIB Request

5
4
Generates
Token

6
 Debits the [Wallet Platform Pool in Sends Token to
DIB] with the fees Beneficiary via
 Credits the Commission P/L with the SMS
fees

 Debits the [Wallet Platform Pool in

DIB] with the total amount
 Credits the [Remit2ATM Wallet
Platform Pool] account with the total
amount

Queue
Notifies Updates its
7 notification for 8
Member Center accounts
Batch File

Formatted: Font: 9 pt, Not Bold, Italic

 Dubai Islamic Bank-IT Department

1218

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 88 of 252
 Dubai Islamic Bank-IT Department

Remit to ATM – Request Token

Subscriber PinPay App PinPay System Member Center DIB System

Initiate Remit to Enters Amount Receives Remit Forwards Processes

1 2 3. Forward to Member Center 4
ATM request to Remit to ATM request request to DIB Request

4
Generates
Token

6
Sends Token to
 Debits the [PinPay Pool in DIB] with
Beneficiary via
the fees
SMS
 Credits the Commission P/L with the
fees

 Debits the [PinPay Pool in DIB] with

the total amount
 Credits the [Remit2ATM PinPay Pool]
account with the total amount

Queue
Notifies Updates its
7 notification for 8
Member Center accounts
Batch File

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 89 of 252
 90

Figure 18 - ATM Cash Disbursement Figure 1319 - ATM Cash Disbursement

 Dubai Islamic Bank-IT Department

Field Code Changed

Subscriber ATM DIB System Member Center

Enters:
Receives Token
- Token Receives Remit
via SMS from 1 2
- Sender Mobile to ATM request
DIB
Number
3

Validates
Transaction

Receives Disburses cash Confirms Cash

6 5
amount to subscriber Disbursement

Notifies Receives
6
Member Center confirmation

DIB updates its

accounts

 Debits [Remit2ATM Wallet

Platform Pool Account]
 Credits [ATM Cash Account]

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 91 of 252
 Dubai Islamic Bank-IT Department

Subscriber ATM DIB System Member Center

Enters:
Receives Token
- Token Receives Remit
via SMS from 1 2
- Sender Mobile to ATM request
DIB
Number
3

Validates
Transaction

Receives Disburses cash Confirms Cash

6 5
amount to subscriber Disbursement

Notifies Receives
6
Member Center confirmation

DIB updates its

accounts

 Debits [Remit2ATM PinPay

Pool Account]
 Credits [ATM Cash Account]

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 92 of 252
 93

ATM Exception – Funds not Withdrawn

Scenario 1
During the Remit to ATM transaction, an exception could occur whereby the subscriber would not withdraw the funds
from the ATM.

To handle this exception, the following would take place:

 Mobile Wallet System will send a validation check to DIB after the cut off to ensure that the transaction process
is successful without issues

 During a Remit2ATM transaction, the beneficiary would be provided with a certain expiration period (2 days
or so) before the transaction would expire. Once the transaction expires, the beneficiary will not be able to
withdraw the funds from the ATM.

 When the expiration period occurs, Wallet PlatformPinPay would cancel the transaction on its end and return
the funds back from the Remit2ATM Wallet PlatformPinPay Pool account to the Wallet PlatformPinPay Pool
SVA account.

 Note that the fees that were initially withdrawn would not be reversed back.

 The subscriber will receive notifications when the expiration period has passed and the reversal request is
complete.

Account Debit Credit

[Remit2ATM Pool Wallet 100 AED
PlatformPinPay]
[Wallet PlatformPinPay Pool in DIB] 100 AED

Scenario 2
If the subscriber withdrew the funds, but the Mobile Wallet system did not receive a notification message, then the
Mobile Wallet system will need to do an inquiry request to validate the transaction.
 Dubai Islamic Bank-IT Department

8.5. Remittance
This service will enable subscribers to transfer money from their Wallet SVA account to subscriber’s located in other
countries. The recipient will be able to withdraw the funds at any DIB appointed cash outlet and agents in foreign
countries.

The transfer will also be made in a foreign currency.

This process needs to be discussed in further details with DIB to finalize the workflow.

Please note that this section will not be included in Phase 1 of the project delivery. It will be included in Phase 2.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 94 of 252
 Dubai Islamic Bank-IT Department

9.6. Cash in through CCDM

This service will enable subscribers to deposit cash through a DIB ATM. The cash will then be deposited into the
recipient’s Wallet SVA account.

Please note that this section will not be included in Phase 1 of the project delivery. It will be included in Phase 12.

Workflow

Step 1
The subscriber must enter his mobile number into the ATM and select to deposit the cash. He enters his Mobile
Number – this is the key.

Step 2
Once the subscriber deposits the cash, a request is sent to the bank to validate the subscriber’s Wallet SVA.

Step 3
Once validated, the bank will notify Wallet PlatformPinPay that the funds have been deposited into the subscriber’s
Wallet SVA.

Step 4
At the end of the day, Wallet PlatformPinPay will be sending DIB a batch file (CCDM Principle Settlement – Recon) that
includes all the transactions conducted. DIB will then update the appropriate accounts:

Account Debit Credit

[Cash deposit Wallet Platform 100 AED
PinPay Pool]
[ Wallet Platform PinPay Pool in DIB] 100 AED

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 95 of 252
 96

Figure 19 - CCDM Workflow Figure 1420 - CCDM

 Dubai Islamic Bank-IT Department

Field Code Changed

CCDM

Subscriber ATM DIB System Member Center

Initiates CCDM Enters Mobile # and Receives CCDM

1 2
Request Deposits cash request

Validates
Transaction

Notifies Subscriber Confirms Cash

5
of successful deposit Deposit

Receives
Notifies
6 confirmation
Member Center
request

DIB updates its

accounts

 Debits [Cash Account in DIB]

 Credits [Cashdeposit Wallet
Platform Pool]
Phase

Receives End of day

settlement file Settlement

 Debits [Cashdeposit Wallet

Platform Pool]
 Credits [Wallet Platform Pool
in DIB]

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 97 of 252
 Dubai Islamic Bank-IT Department

CCDM

Subscriber ATM DIB System Member Center

Initiates CCDM Enters Mobile # and Receives CCDM

1 2
Request Deposits cash request

Validates
Transaction

Notifies Subscriber Confirms Cash

5
of successful deposit Deposit

Receives
Notifies
6 confirmation
Member Center
request

DIB updates its

accounts

 Debits [Cash Account in DIB]

 Credits [Cashdeposit PinPay
Pool]
Phase

Receives End of day

settlement file Settlement

 Debits [Cashdeposit PinPay

Pool]
 Credits [PinPay Pool in DIB]

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 98 of 252
 99

10.7. Cash in / Out through Agent

The service will enable subscribers to deposit and to withdraw cash through an appointed DIB Agent.

 Cashing in will deposit the funds into the subscriber’s Wallet SVA account
 Cashing out with will withdraw the funds from the sender’s Wallet SVA account

Note that both functions require further discussion with DIB to finalize the processes.

This section will not be included in Phase 1 of the project delivery. It will be included in Phase 2.
 Dubai Islamic Bank-IT Department

11.8. Mobile POS Payment

The M-POS is a merchant controlled app that billers can use in order to process payments from their subscribers. The
app is available in the actual POS machine that will be provided to billers, and can also be downloaded into an Android
device.

Billers can process payments and print receipts through the M-POS.

Activating M-POS Terminals

When receiving the M-POS app, the biller will be asked how many terminals he requires. These terminals will have a
unique code that the biller must enter into the terminal in order to activate it.

The unique code that will activate the terminal will be at least 15 digits long. It should be noted that the biller cannot
re-download the app on the terminal – he must contact the bank in order to reset it.

There are two different processes available for the M-POS purchase solution:

 M-POS Purchase – Push Workflow

 M-POS Purchase – Pull Workflow

M-POS Services
This section will detail the M-POS service offered by Wallet PlatformPinPay:

 Create Orders
 Manage Orders
 View Reports

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 100 of
252
 Dubai Islamic Bank-IT Department

Create Orders

When subscribers perform a purchase at the biller, there are two ways in which the transaction can be conducted via
the M-POS:

1. M-POS Purchase via Scanning Code

2. M-POS Purchase – Manual Entry

M-POS Purchase – Scan Code Workflow (Push)

This method requires the biller to scan the barcode displayed on the subscriber’s WalletPinPay app. The process is
detailed below:

Step 1
The subscriber enters the bill amount (selects currency as well) and his M-PIN into the app.

Step 2
The PinPay Wallet app will generate an OTP and display a barcode. The barcode includes all the OTP information
required.

Step 3
The biller will then use his M-POS to scan the barcode displayed on the subscriber’s PinPay Wallet App.

Step 4
The transaction is sent to the PinPay SystemWallet Platform, where the OTP information is verified and the
transaction processed.

Step 5
Once the transaction is processed, Wallet PlatformPinPay will send a notification back to the M-POS to confirm the
transaction.

Wallet PlatformPinPay will also send a notification to the subscriber via SMS to notify him of the successful
transaction.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 101 of
252
 102

Figure 20 - M-POS Purchase (Scan Code) Figure 1521 - M-POS Purchase (Scan Code)
 Dubai Islamic Bank-IT Department

M-POS Purchase – Scanning Code

Subscriber PinPay App M-POS PinPay System

Subscriber enters
App generates an
the bill amount and
1 OTP as a barcode or
his M-PIN into the
QR code
app

Biller scans the

Subscriber displays Receives transaction
3 barcode using the M- 4
barcode to Biller request
POS scanner

Validates the OTP

information

Processes request

Displays success
8. Sends response to M-POS Sends notification
response

Displays success
9. Sends response to Subscriber via SMS
ITPMO-INI-002 response Version 1.2, June 2015
Controlled Document For Internal Use Only Page 103 of 252
 Dubai Islamic Bank-IT Department

Field Code Changed

M-POS Purchase – Scanning Code

Subscriber DIB Wallet M-POS Wallet Platform

Subscriber enters
App generates an
the bill amount and
1 OTP as a barcode or
his M-PIN into the
QR code
Wallet app

Biller scans the

Subscriber displays Receives transaction
3 barcode using the M- 4
barcode to Biller request
POS scanner

Validates the OTP

information

Processes request

Displays success
8. Sends response to M-POS Sends notification
response

Displays success
9. Sends response to Subscriber via SMS
response
ITPMO-INI-002 Version 1.2, June 2015
Controlled Document For Internal Use Only Page 104 of 252
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 105 of 252
 106

M-POS Purchase – Manual Entry Workflow (Push)

For any reason the scanning process fails, the biller will be able to enter the payment information manually into the
M-POS.

He would be required to enter the following information into the M-POS:

 OTP
 Subscriber’s Mobile Number
 Bill Amount with Currency

Step 1
The subscriber enters the bill amount (selects currency as well) and his M-PIN into the app.

Step 2
The PinPay Wallet app will generate an OTP and display a barcode. The barcode includes all the OTP information
required.

Step 3
The biller will then enter the following into the M-POS:

 OTP
 Subscriber’s Mobile Number
 Bill Amount with Currency

Step 4
The transaction is sent to the PinPay SystemWallet Platform, where the OTP information is verified and the
transaction processed.

Step 5
Once the transaction is processed, Wallet PlatformPinPay will send a notification back to the M-POS to confirm the
transaction.

Wallet PlatformPinPay will also send a notification to the subscriber via SMS to notify him of the successful
transaction.

Note the following notifications that the subscriber may receive via SMS:
 Successful Payment
 Failed Payment General Error
 Failed Payment – Invalid OTP
 Failed Payment – Invalid Mobile Number entered
 Failed Payment – Insufficient Funds
 Failed Payment – Limit Reached
 Failed Payment – Payment reversed successfully
 107

Figure 21 - M-POS Purchase (Manual Entry) Figure 1622 - M-POS Purchase (Manual Entry)

Field Code Changed

M-POS Purchase – Manual Entry

Subscriber DIB Wallet M-POS Wallet Platform

Subscriber enters
App generates an
the bill amount and
1 OTP as a barcode or
his M-PIN into the
QR code
Wallet app

2
Biller enters the following into
the M-POS:
Subscriber displays - OTP Receives transaction
3 4
barcode to Biller - Subscriber s Mobile Number request
- Bill Amount
- Select Currency
5

Validates the OTP

information

Processes request

Displays success
8. Sends response to M-POS Sends notification
response

Displays success
9. Sends response to Subscriber via SMS
response

Formatted: Font: 9 pt, Not Bold, Italic

 Dubai Islamic Bank-IT Department

M-POS Purchase – Manual Entry

Subscriber PinPay App M-POS PinPay System

Subscriber enters
App generates an
the bill amount and
1 OTP as a barcode or
his M-PIN into the
QR code
app

2
Biller enters the following into
the M-POS:
Subscriber provides
- OTP Receives transaction
biller with payment 3 4
- Subscriber s Mobile Number request
details
- Bill Amount
- Select Currency
5

Validates the OTP

information

Processes request

Displays success
8. Sends response to M-POS Sends notification
response

Displays success
9. Sends response to Subscriber via SMS
response

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 108 of 252
 109

M-POS Purchase – Scan Code Workflow (Pull) Formatted: Heading 4

This method requires the subscriber to scan the barcode (QR) presented by the biller. The subscriber must create the
payment voucher in this case. The process is detailed below:

Step 1 Formatted: Justified

The subscriber initially creates a payment voucher by entering the bill amount, selecting the currency and entering his
M-PIN into the app.

Step 2
The biller will prepare the payment order on his M-POS and generate a barcode that the he displays to the subscriber.
The barcode includes all the OTP information required.

Step 3
The subscriber will then use his Wallet App to scan the barcode displayed on the biller’s M-POS.

Step 4
The transaction is sent to the Wallet Platform, where the OTP information is verified and the transaction processed.

Step 5
Once the transaction is processed, Wallet Platform will send a notification back to the M-POS to confirm the
transaction.

Wallet Platform will also send a notification to the subscriber via SMS to notify him of the successful transaction.
 110

Formatted: Keep with next

Figure 1723 - M-POS Purchase (Pull) Formatted: Width: 11.69", Height: 8.27"
Formatted: Caption

Field Code Changed

M-POS Purchase – Scanning Code (Pull)

Subscriber DIB Wallet M-POS Wallet System

Subscriber enters
Subscriber selects to the bill amount,
Biller generates
create Payment 1 select the currency 2
barcode on M-POS
Voucher and entering and his
M-PIN into the app
3

Subscriber scans the Biller displays

barcode using his 4 barcode to
Wallet App Subscriber

Receives transaction
5
request

Validates the OTP

information

Processes request

Displays success
9. Sends response to M-POS Sends notification
response

Displays success
9. Sends response to Subscriber via SMS
response
 111

Formatted: Justified

Manage Orders

Billers can inquire the status of any conducted purchase by entering the RRN Number of the transaction. The M-POS
will return the transaction details as well as the status – whether it was successful or not.

The biller can also conduct a Refund request transaction that will return the funds back to the subscriber.

View Reports

The M-POS also provides the biller with a complete overview on the number of transactions conducted on the
terminal, as well as the total amount of the transactions.

The biller can select on the “Show Graph” button in order to view a simple graph that displays the total number of
transactions conducted on a monthly period.
 Dubai Islamic Bank-IT Department

12.9. Web Checkout

Wallet PlatformPinPay will provide its billers with the web checkout service that will enable subscribers to conduct
payments on biller websites using the PinPay Wallet app.

It should be noted that subscribers can only conduct web checkout transactions using any of their linked accounts.

The Wallet PinPay web checkout service is already integrated with the following websites as a payment gateway.
Billers who have websites in the following platforms will be able to select Wallet PlatformPinPay as a payment gateway
to process transactions:

 Magento
 Open Cart

Web Checkout SDK

Billers can also receive the Web Checkout SDK from Wallet PlatformPinPay and integrate the code into their individual
websites. Doing so will activate the PinPay Wallet web checkout service that would enable subscribers to make
purchases using their PinPay Wallet app.

Workflow

Step 1
Subscriber conducts a purchase on the biller’s website and lands in the check-out page. The page displays the total
amount that will be charged as well as an entry box for the OTP.

Step 2
Subscriber enters the bill amount and his M-PIN into the PinPay Wallet app. An OTP is generated and the subscriber
enters it into the website OTP entry box.

Step 3
The purchase request is submitted and is sent to the PinPay SystemWallet Platform. The PinPay systemWallet Platform
receives the transaction request and validates the information sent.

Step 4
Once validated, the PinPay systemWallet Platform returns a response back to the biller’s website. The subscriber is
also notified of the transaction result via SMS.

Note the following notifications that the subscriber may receive via SMS:
 Successful Payment
 Failed Payment General Error
 Failed Payment – Invalid OTP
 Failed Payment – Invalid Mobile Number entered
 Failed Payment – Insufficient Funds
 Failed Payment – Limit Reached
 Failed Payment – Payment reversed successfully

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 112 of
252
 113

Figure 22 - Web Checkout Figure 1824 - Web Checkout

Field Code Changed

Web Checkout

Subscriber DIB Wallet Biller Website Wallet Platform

Subscriber enters OTP and

Subscriber enters
App generates an Mobile Number into
the bill amount and
1 OTP as a barcode or 2 website or Scan QR Code
his M-PIN into the
QR code generated on web
Wallet app
checkout

Purchase request
Receives transaction
sent to Wallet 4
request
Platform

Validates the OTP

information

Processes request

Displays success 8. Sends response to Biller

Sends notification
response Website

Displays success
9. Sends response to Subscriber via SMS
response
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 114 of 252
 Dubai Islamic Bank-IT Department

Web Checkout

Subscriber PinPay App Biller Website PinPay System

Subscriber enters
App generates an Subscriber enters
the bill amount and
1 OTP as a barcode or 2 OTP and Mobile
his M-PIN into the
QR code Number into website
app

Purchase request
Receives transaction
sent to PinPay 4
request
System

Validates the OTP

information

Processes request

Displays success 8. Sends response to Biller

Sends notification
response Website

Displays success
9. Sends response to Subscriber via SMS
response

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 115 of 252
 116

13.10. Wallet Services

Subscribers would be able to manage their wallet services through the PinPay Wallet app. The different functionalities
that the subscriber can perform are:

 Control frequency of transactions

 Configure transaction limits
 Balance Inquiry
 Transaction Statements
 Reports (Loyalty)

Please note that this section will not be included in Phase 1 of the project delivery. It will be included in Phase 2.

Transaction Frequency

Subscribers will be able to control the frequency of his conducted transactions through the PinPay Wallet app. There
will be a section in the app that will enable subscribers to set and edit the velocity allowed to conduct transactions.

Configurable Transaction Limits

Subscribers will be able to configure their own transaction limits through the PinPay Wallet app. There will be a section
in the app that will enable subscribers to set and edit limits allowed for each transaction.
 Dubai Islamic Bank-IT Department

14.11. Transaction History and Summary Balances

The Payment History section of the PinPay Wallet app provides subscribers with a complete overview of all the
transactions that he has conducted through the app. The information that the subscriber can view include:

 Incoming Money Transactions

 Outgoing Money Transactions
 Money Received
 Money Sent
 Payment History
 Vouchers

Incoming Money Transactions

All incoming money transfers made to the subscriber are logged here. These transfers are still pending acceptance and
the subscriber can choose to accept and reject the transaction from this section.

The details of the transfer are also displayed, including the sender’s details and the amount transferred.

Outgoing Money Transactions

All outgoing transfers made from the subscriber to his recipient are logged here. These transactions have not yet been
accepted by their recipients. The subscriber can select to cancel the transfer from this section.

The details of the transfer are also displayed, including the recipient’s details and the amount transferred.

Money Received
All money transfers successfully accepted by the subscriber are logged here.

Money Sent
All money transfers successfully sent by the subscriber and accepted by the recipient are logged here.

Payment History
All the payments conducted by the subscriber are displayed in this section. It includes the payment details, such as the
date of the transaction, the provider (example: Etisalat Recharge), the amount, the source account (example: CASA)
as well as any other details that relate to the nature of the transaction itself (example: Etisalat Recharge Voucher
Code).

Subscribers can search the list for specific transactions in the search bar available.

Vouchers
There is a specific section on the app that displays the history of all the different vouchers that the subscriber has
purchased. The vouchers are displayed in a card-format and will include the voucher details, such as the amount,
voucher code etc.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 117 of
252
 Dubai Islamic Bank-IT Department

15.12. System Settings

Subscribers can control certain features of their app through the settings section. The features that can be managed
include the following:

Facebook Linking
Subscribers can link their Facebook accounts to their PinPay Wallet app through this section.

M-PIN Management
Subscribers can change their M-PIN in this section of the app.

Enable Login with Touch ID (for iPhone only)

Subscribers can enable or disable the touch ID to login and confirm transactions.

Devices
Subscribers can manage their linked devices through this section. They can delete certain devices – doing so will
remotely unregister the Wallet PinPay service for the subscriber from that device.

Add an Email
Subscribers can link the email address to the PinPay Wallet app through this section.

Quick Pay
This option enables subscribers to delete all their saved transactions at Quick Pay.

Update Info
If there are any updates that subscriber can perform, it will be listed here. (Example: Link Email).

Unregister this Device

Subscriber can manually unregister his device. Doing so will require the subscriber to re-register his device if he
wishes to use Wallet PinPay in the same device.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 118 of
252
 Dubai Islamic Bank-IT Department

16.13. App Design

PinPay has recruited a UX design consultant who would be leading the revamping of the PinPay front end interface to
meet the requirements set forth by PinPay and DIB.

The UX design expert is in the process of creating a proposed app design. Once ready, we will be presenting it to DIB
for discussion and feedback. The revamp will include major app enhancements that will transform PinPay into a more
engaging, interactive and seamless app, with a modern and fresh look-and-feel.

The UX design of the wallet app has to be led by an experienced design consultant and presented to DIB and
incorporate all the DIB theme and should be an engaging, interactive and seamless app, with a modern and fresh
look-and-feel.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 119 of
252
 Dubai Islamic Bank-IT Department

17.14. Offers & Deals Catalog

Subscribers can view different offers and deals presented on the PinPay Wallet app. Subscribers will be able to do the
following:

 View offers and deals catalog

 Save offers and deals
 Redeem offers and deals

The presentment of the offers and deals will be discussed during the redesign of the PinPay app to align with the
engagement and interactive requirements set forth by DIB and PinPay.

Qubify Offer and deals Interface System

The Offer and deals portalQubify component will be responsible for pushing the offers and deals to the Wallet.

View Offers and Deals

Subscribers will be able to view different offers and deals on the PinPay Wallet app. Promotional content are pushed
by DIB and/or the biller using the Offer and deals portalQubify component.

Save Offers and Deals

Subscribers can save offers as coupons on their Wallet SVA’s. They will access them from the wallet during
redemption.

Redeem Offers and Deals

Subscribers can redeem their offers and deals. The redemption process will be discussed at a later stage.

Note that the offers and deals segment of the overall PinPay Wallet offering will not be available in Phase 1. It will be
available in Phase 2.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 120 of
252
 121

Bank Portal
The purpose of this section of the BRD is to detail the business requirements for the Bank Portal interface that
PinPay Wallet platform will provide to Dubai Islamic Bank (DIB) as part of the DIB Mobile Wallet project.

This document will therefore be illustrating the minimum business requirements that would be available in the Bank
Portal.

The different back-office components and features that will be outlined in this section of the BRD are:

Back-Office System Components:

 Bank Portal
o Content Management
o Notification Management

Additional Feature:

 Risk Management
 Compliance
 Dubai Islamic Bank-IT Department

Bank Portal Features

The Bank Portal is a web-based back office system that will be used by DIB bank users to onboard/manage subscriber
wallet SVA’s, onboard/manage merchants, perform reconciliation and settlement procedures and handle disputes.

The bank portal therefore provides DIB bank users with a single interface in order to manage all tasks and
functionalities related to both the subscriber and the merchant.

The main sections available in the Bank Portal are:

 Administration
 Subscriber Management
 Biller Management
 Content Management
 Notification Management (Email/SMS)
 Bank Settings

Each section will be illustrated in further details.

Maker / Authorizer

DIB bank users who access the Bank Portal will either have a Maker or an Authorizer role. Each role grants the user a
set of privileges that will enable him to perform specific functions on the Bank Portal.

 The maker role enables users to create, manage and request modifications on different aspects related to
the subscriber or merchant.

 The authorizer role enables users to confirm change requests, enrollment processes and other activities
related to the subscriber or merchant.

In some instances, certain activities done on the portal by the maker may require an approval from an Authorizer to
fully execute the activity.

For example: Subscriber enrollment through the Bank Portal can be initiated by the maker. However, after a certain
point of the enrollment process, an authorizer would be required to approve the subscriber registration. The
subscriber would therefore only be fully registered once the authorizer confirms the enrollment request.

Queues

The Bank Portal will contain different queues that are detailed further in this document. These queues will log in
various modifications and requests conducted by DIB bank users with a Maker role.

A different user with an authorizer role will review the requests recorded in the various queues to either approve or
reject.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 122 of
252
 Dubai Islamic Bank-IT Department

1. Administration
The Administration section of the Bank Portal will enable DIB bank users to create new users, manage existing users
and assign maker/checker roles.

 User Management
 Role Management
 Privilege Management
 User Management Reports

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 123 of
252
 124

User Management

This feature enables DIB bank users to add new users who will have access to the Bank Portal to perform specific functions. The new user can have a maker or authorizer
role. The administrator user level will only have user and access related functions. This user level will not have business related functions nor transaction functions At the
same time, users that have transaction level functions will not have any user/access related functions.

When entering this section of the Bank Portal, DIB bank users can view a list of available users already added. They would be able to:

 Edit – edit each user’s information, and request to reset the user’s password
 Activate / Deactivate – enable or disable the user’s status
 Add new user
 125

Add a New User Workflow

Step 1
To add a new DIB bank user, the admin must enter the First Name and Last Name of the new user. The admin must also enter the Bank User ID.

Step 2
Enter the email address of the new user.
 126

Step 3
Select the role of the new user – some of the levels include:

 Maker – for example (CSO): This is mainly for creation of plans, services, managing fees and pricing etc.
 Authorizer – for example (E-Banking Supervisor): This is mainly used for subscriber registration, management etc.

Step 4
After submitting the required information, the new user will receive a notification email stating he/she was enrolled as a user on the Member Center

Step 5
The new user must confirm his account by clicking on the link found in the confirmation email.
 127

Role Management

In this section, the admin can create new roles and define whether the role is a maker or authorizer.

When creating users, the admin will assign the user a role of whether he is a maker or authorizer.
 128

Privilege Management

The admin must select the functionalities allowed for each role. Depending on the role type (maker/authorizer), only
the specific functions that are allowed for each category can be selected.

User Management Reports

The following reports should be available:

 List of users stating their roles, functions and statuses

 Complete changes audit for users and groups
 Dubai Islamic Bank-IT Department

2. Subscriber Management
The Subscriber Management section of the bank portal will enable DIB bank users to perform various tasks related to
their subscribers and their SVA’s.

The main functionalities to be included in the Subscriber Management section are:

 Enrollment
 Inquire Subscriber
 Plan Management
 Plan Configuration Queue
 P2P Transactions
 P2P Transactions Queue
 Refunds Queue
 Unload SVA Queue
 Disputes Management Queue
 Reports

Maker / Authorizer Activities

As mentioned previously in the Maker/ Authorizer section of the document, certain functionalities and activities that
are performed on the Bank Portal may require single or dual authentication to fully complete the function.

The matrix below therefore highlights the maker/authorizer activities that can be done in the Subscriber Management
section of the portal, as well as the appropriate queue they will end up in:

# SVA Activities Execution Queue

1 New Enrollment Dual Authentication Enrollment Queue
2 Unload SVA Dual Authentication Unload SVA Queue
3 P2P Transaction Dual Authentication P2P Transaction Queue
4 Refund Transaction Dual Authentication Refund Queue
5 Plan Management Dual Authentication Plan Configuration Queue
6 Block / Activate Wallet Single
7 Update Customer Profile Single
8 Send Notification (Email / SMS) Single
N/A
9 Remove Device Single
10 Unlink Card / Account Single
11 Agent Cash in / Cash Out Single

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 129 of
252
 Dubai Islamic Bank-IT Department

Enrollment

DIB bank users can onboard subscribers through the Bank Portal. Subscribers that can onboard to the PinPay Wallet
service can be classified into the following market segments:

 Residents
o DIB Customers
o Non-DIB Customers
 Visitors

It should be noted that the onboarding process is a dual execution one, requiring both a maker and an authorizer to
complete the registration from end-to-end.

Back Office Onboarding

Subscribers can enroll to the PinPay Wallet service by visiting a DIB branch or DIB appointed Agent and filling in the
registration application form. Both residents and visitors have this onboarding option.

The back office onboarding process can be done on an individual level and in bulk – in the case that the DIB bank user
wishes to onboard a large number of subscribers at a single time.

For more information on the onboarding process, please refer to the document: BRD (1/3) – Mobile Wallet v.01

Enrollment Queue

Once the DIB Bank user (the maker) has submitted the application form, the enrollment request will be logged in the
Enrollment Queue. A DIB bank user with an authorizer role will have to approve the request in order to complete the
enrollment process and create the subscriber’s profile and Wallet SVA.

This section will have three different types of queues to log the following:

 Subscriber Creation – for successful screening and KYC. Requires authorizer approval. Subscriber creation
requests can originate from the back-office enrollment or through the self-registration process.
 Screening Failed – requires revision
 KYC Failed – requires revision

In case of a failed screening or KYC, the authorizer will have to investigate and take appropriate action. The
authorizer can either approve or reject the registration. He can include his comments in his decision.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 130 of
252
 131

Inquire Profile

DIB bank users would need to inquire a subscriber in order to view his profile and transaction information. Bank users may inquire a subscriber’s details in order to investigate
and resolve any issues or complaints that are raised from the subscriber.

Inquire Process

The DIB bank user must search for an existing subscriber in order to perform subscriber specific functions. To do so, he must first enter the subscriber’s search information.

Step 1
DIB bank user accesses the Inquire Subscriber section of the portal and must enter one or all of the following:

# Search Criteria
1 First Name and Last Name
2 Mobile Number
3 Email Address

Note that if a subscriber calls in to inquire any information or raise a dispute, he is required to provide his mobile number. If he fails to do so, he will have to answer several
securityseveral security questions that is displayed in his profile, such as the subscriber’s:

 Mobile Number
 Email AddresAddress
 Passport Number / Emirates ID
 Nationality

Step 2
When the search results are displayed, the bank user can then select the subscriber from the list provided.
 132

First Name Last Name Mobile Number Email Search

Name Mobile Number CIF ID Service Plan Status

Name 1 +971561230456 4579456 Pre-KYC Blocked View Profile
Name 2 +971567481595 4164649 Post-KYC Deceased View Profile
Name 3 +971502594564 2486406 Gold Plan Inactive View Profile
Name 4 +971552179645 1306854 Platinum Plan Dormant View Profile
Name 5 +971589741543 1679105 Diamond Plan Active View Profile
 Dubai Islamic Bank-IT Department

Step 3
Selecting the subscriber will take the bank user to a new dashboard screen for the specific subscriber – the Subscriber Dashboard screen. The following information are
displayed on the Subscriber Dashboard detailed below:

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 133 of 252
 134

Subscriber Dashboard

DIB Bank users can perform a number of activities on the subscriber’s profile after inquiring it. Each functionality is
briefly described below.

A. Profile Information
The subscriber’s key profile information are displayed in a table, including his mobile number, CIF, Email address,
Profile status and plan that he is linked to.

B. View Additional Info

The user can select to view additional information, which would result in a broader overview of the subscriber’s profile.

C. Edit
The user can also select to edit the subscriber’s information.

 User can upgrade or downgrade the subscriber’s plan by selecting the new plan from the drop-down list
provided.

D. Summary Tables
The summary tables will display a summary of the subscriber’s transactions and profile limits.

The transaction table will display the subscriber’s last 5 transactions conducted. The transactions displayed are
prioritized according to whether the transaction was successful or not – failed transactions will show first to provide
the user with quicker access in the resolution process.

The user can select each transaction in order to get a more detailed overview of it.

The profile limit tables will display whether the subscriber has exceeded any of his limits.

E. Block/Activate
Enables the DIB bank user to block a subscriber and reactivate a blocked subscriber.

F. Cancel
Enables the DIB bank user to cancel a subscriber’s PinPay Wallet membership.
 135

Accounts

The accounts tab on the header will enable DIB bank users to view all the accounts linked to the subscriber in a table format.

Selecting each account will display a more detailed overview of each account type as well as the allowed actions for each type.
 136

G. SVA Accounts

After selecting on an SVA account, the user can perform the following:

View Balances
The user can view the balances for the SVA accounts. Balances are only displayed for SVA accounts.

Unload SVA
Select to unload the funds contained in the subscriber’s Wallet SVA account back to his CASA. Note that this process requires a dual authorization in order to execute.

That means that after selecting the Unload SVA button, the request is logged in the Unload SVA Queue.

An authorizer with the authority to execute an unload SVA transaction will access the Unload SVA Queue and either approve or reject the unload SVA request.

Close SVA
DIB bank users can close a subscriber’s Wallet SVA account.
 137

Figure 23 - Unload SVA Workflow Figure 1925 - Unload SVA Workflow

Unload SVA
Change Request Change Approval

Inquire Subscriber
Profile

Selects on Accounts

Selects on the
specific SVA account

Selects on Unload
SVA function

User selects
destination CASA

Selects on Unload
SVA

Request is submitted
and is logged in the 7 User views requestt
Unload SVA Queue
8

User approves the

Unload SVA request

The request status is

then closed

10

The subscriber is
notified of the
update
Phase
 Dubai Islamic Bank-IT Department

H. CASA and Credit Card Account

After selecting either the CASA or Credit Card account from the table, the user can perform the following:

Transaction ID Payment Type Bill Amount Fees Total Amount Record Date Status
46189 Emaar Bill 501 12 513 15/12/2016 12:15 PM Failed Submit Claim
16745 RTA 900 12 912 2/12/2016 8:05 AM Failed Submit Claim
32566 Etisalat Recharge 150 5 155 25/12/2016 6:28 PM Profile Limit Reached! Submit Claim
36565 Etisalat Postpaid 300 10 310 19/12/2016 4:44 PM Profile Limit Reached! Submit Claim
46514 Ajman Sewerage 600 30 630 03/01/2017 9:32 AM Successful Submit Claim

Unlink

Transaction ID Payment Type Bill Amount Fees Total Amount Record Date Status
46189 Emaar Bill 501 12 513 15/12/2016 12:15 PM Failed Submit Claim
16745 RTA 900 12 912 2/12/2016 8:05 AM Failed Submit Claim
32566 Etisalat Recharge 150 5 155 25/12/2016 6:28 PM Profile Limit Reached! Submit Claim
36565 Etisalat Postpaid 300 10 310 19/12/2016 4:44 PM Profile Limit Reached! Submit Claim
46514 Ajman Sewerage 600 30 630 03/01/2017 9:32 AM Successful Submit Claim

Unlink

Unlink Account/Card
The user can unlink the account or card of the subscriber from his WalletPinPay membership.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 138 of
252
 139

Transaction History

DIB bank users can view the history logs of all the transactions conducted by the specific subscriber. The user can search by date, account type, payment type name and
transaction status.
 Dubai Islamic Bank-IT Department

The user can perform the following functions in the subscriber’s transaction history page:

I. Submit Claim

Select to submit a claim for any of the transactions displayed if required. The claim process is further detailed in the Claims section of this document.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 140 of 252
 141

J. Refund Request
Some claims may require a refund request and approval process.

Step 1
The DIB bank user (this user could be a different one that the user who originally submitted the claim) will access the Claims tab in order to view all claims.

Step 2
After investigation, the user can select to Refund the subscriber’s transaction if the resolution requires a refund. User accesses the subscriber’s transaction history,
identifies the specific transaction that requires the refund and then selects on Request Refund button for this specific transaction.

The Refund request is now in pending approval status.

Step 3
The refund request is sent to the Refund Queue and PinPay Wallet Platform will review the request and approve it.

Step 4
The refund transaction request then enters the actual refund queue to be settled in the next settlement period.
 Dubai Islamic Bank-IT Department

Figure 24 - Refund Workflow Figure 2026 - Refund Workflow

Formatted: Normal
Formatted: Font: 11 pt, Not Bold, Italic

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 142 of 252
 Dubai Islamic Bank-IT Department

Profile Status History

DIB bank users can view the history logs of all the status changes effecting the specific subscriber. Each log will provide an overview of the subscriber’s current status, including
his linked accounts, plan linked etc.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 143 of 252
 144

Profile Limits

DIB bank users can view the profile limits linked to the subscriber’s profile.
 145

Manage Devices

DIB bank users can manage the devices of subscribers that are linked to the PinPay Wallet service. Note that this
process is a single authorization one.

The following functionalities can therefore be performed in this section:

Max Number of Devices

DIB bank users can view the number of devices linked to the subscriber.

Remove Device
Users can select to disable a certain device. Disabling a device will prevent the subscriber from accessing the PinPay
Wallet app on the disabled device. Users can also enable a disabled device, allowing the subscriber to access
PinPayWallet.
 146

Send Notifications

There is a function available that will enable DIB bank users to send a notification to the specific subscriber if required. The user can send an email and SMS to the individual
subscriber and would only have to enter the text for the notification message and submit it.

Note that this process is a single authentication one.

 147

Claims

The Claims tab of the subscriber’s dashboard will contain a list of all claims that were submitted by DIB bank users.
Users can view the claims and follow up on the issues before closing it.

The number of open claims are displayed as notifications.

K. Dispute Management
The types of claims that can be submitted depends on the dispute that was raised by the subscriber. The types of
disputes available are:

# Claim Type Description

1 Item not Received (INR)  Subscriber’s account was debited
 Service not rendered
2 Duplicate Transaction  Subscriber’s account was debited twice
 Service rendered twice
3 Incorrect Consumer Credit

Note that more claim types will be added.

Disputes can be raised in two ways:

 By the subscriber from the PinPay Wallet app itself
 Subscriber calling the DIB Bank Support Center to raise the issue

The user must search and identify the transaction that has any of the above issues and select to submit a claim.
Submitted claims are automatically logged for users to investigate and follow up on.

Submitting Claims
Claims are recorded in two sections of the Bank Portal:

 In the Claims section of the subscriber dashboard for each individual subscriber
 The same claim is also recorded in the Disputes Management section of the Bank Portal

Closing Claims
Once a claim has been submitted, PinPay Wallet platform will handle the resolution process. The functionalities that
both user types can perform in the Claims section of the subscriber dashboard and in the Dispute Management are
detailed below:

# User Type Functions

1 DIB Bank User  View claim statuses – whether open or closed
 Follow up with PinPay Bill desk support unit “Wallet platform
users) – As PinPay they will take the appropriate actions to resolve
the claim, DIB bank users can follow up with PinPay if necessary.
2 PinPay Wallet Platform User  Investigate the issue
 Take action (Refunds)
 Close the Claim
 Notify the Bank and the User of the claim result
148
 149

Submit Claim Workflow

Claims are submitted on a transaction level. The following details the process in which DIB bank users can submit the claim for disputes reported via the Support Center.

Step 1
DIB bank user receives a complaint from a subscriber in the Support Center. The user accesses Inquire Profile section of the Bank Portal and enters the search criteria for
the subscriber calling in.

Step 2
After selecting the subscriber and entering the Subscriber Dashboard, the user can either select the failed transaction from the Alert section of the Bank Portal if it is
displayed, or he can access the Transaction History tab and search for the transaction in question.

Step 3
Once the transaction details are displayed, the user can select to Submit Claim. A window will pop-up asking the user to select the Claim Type from the list provided.

He would then need to enter a brief description of the claim in the text box provided. Once done, he selects to submit the claim.

Step 4
The claim is logged in the Claim tab of the Subscriber Dashboard and on the Disputes Management of the bank portal. The claim status is flagged as open until resolved.
 150

Close Claim Workflow

A DIB Bank user can follow up on an open claim, but only a PinPay Wallet platform user can close one after
resolution.

Step 1
Wallet platformPinPay user investigates the claim that was logged in in the Disputes Management section. After
looking into the issue, the user may decide that the appropriate action to take place would be to refund the
transaction back to the subscriber.

Step 2
Wallet platformPinPay user then takes the appropriate action and refunds the transaction.

Step 3
Wallet platformPinPay user then changes the status of the claim to closed and enters the reason for resolution. A
notification is sent to the bank and to the subscriber informing both parties of the claim status update.
 Dubai Islamic Bank-IT Department

Plan Management

The Plan Management section of the bank portal will enable DIB bank users to create new plans to link their subscribers
to and manage existing ones.

An additional feature that was not stated in the provided BRD will be added - the Frequency.

Frequency
DIB users must enter the allowed transaction frequency for each plan. This defines the amount of time allowed
between each transaction conducted by the subscriber. Performing a transaction before the time allowed will result
in a failed transaction.

Plan Management Queue

Creating a new plan or modifying an existing one requires a dual authentication execution process. Therefore all plan
requests are logged into the Plan Management Queue for an authorizer to review and approve/reject.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 151 of
252
 152

Plan Creation Workflow

To create a plan, the DIB bank user must first click on the Plan Management section of the Bank Portal. Doing so will display the available plans already created in a table
form.

Existing Plans
The existing plans are displayed in a table form. They include the following information that define the plan:
 Plan Name
 Enabled/Disabled – whether the plan is enabled
 Status – whether the plan is approved or rejected.
 Record Date – date on when the plan was last created/modified

DIB bank users can edit current plans, and add new ones.

To create a plan, DIB bank users must enter a set of information onto the portal and configure its properties. There are five main stages in creating a plan:

Stage Description
Plan Definition User must enter general information regarding the plan’s definition
Collection Accounts User must enter the collection account numbers
Service Fees User must configure the pricing for each payment type included within the plan
Subscriber Limits User must define the limits for each Account Type
Subscription Fees User must configure the fees for the subscriber

User selects on the add plan button. The plan creation process is detailed below.
153
 154

L. Plan Definition

Step 1
User selects whether the plan is enabled or disabled

Step 2
User enters the Plan Name

Step 3
User selects the Customer Segmentation to include within the plan. Bank users can link single or multiple customer segments to available plans.

An example of the different customer types available are:

 VIP subscribers
 Bank Employee subscribers
 Regular subscribers
 Youth subscribers

Each of the customer segments are mapped to a customer segment table located at the PinPay systemWallet Platform.

Step 4
User selects the Account Types he wishes to include within the plan. Subscribers linked to the plan will only be able to conduct purchases using the account types defined
within the plan.
155
 156

M. Collection Accounts

The DIB bank user will be able to configure collection account number. The amounts of conducted transactions will be collected in the collection account number defined in
this section.

Note that all DIB accounts undergo a validation process from the Flex before they are committed on the Portal.

Account Number Description

Collection Account Account that collects all transaction amounts conducted by subscribers on DIB billers

N. Services Fees

The stage involves configuring the pricing of each payment type included within the plan.

Step 1
User must select the Billing types from the list provided. User then clicks on Load Payment Type to load all the payment types linked to the Billing types.

Step 2
User must then select which payment types to enable within the plan.
157
 158

Step 3
If a Pricing Template exists, the user can decide to link the payment type to the created pricing template by selecting it on the drop-down list. The system will load the
predefined fees from the pricing template for each account type. The DIB bank user can select to edit any of the pricing data if required.

If the user wishes to configure the pricing manually, he can keep the Template Pricing field empty.

User then selects on Apply Subscriber Pricing in order to configure the pricing for each payment type

Step 4
DIB bank user must configure the pricing for each account type. This process is explained in more detail in the Account Type Pricing section of this document.

 Has Brackets – must define the min and max amounts, and select whether there the pricing is percentage or fixed
 Without Brackets – must select whether pricing is percentage or fixed and define the amount
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 159 of 252
 160

O. Subscriber Limits

The DIB bank user should now define the limits for each account type available in the plan. When defining limits, the user must configure the limit definition for each Limit
Code.

Every Payment Type has a Limit Code that is linked to it. The limits defined for each Limit Code is applied to the associated Payment Type.

For example:
 Account Type: Wallet SVA
 Limit Code: EDU
 Payment Types linked to EDU:
o GEMS Jumeirah Primary School – Dubai
o GEMS Winchester School – Dubai
 Limits defined for EDU are therefore applied to all payment types linked to the Limit Code.
 When the user conducts a transaction for a payment type linked to the Limit Code using his Wallet SVA, the limits defined for this combination is applied.

Step 1
User selects Account Type from list provided.

Step 2
User must then select the Limit Codes that is mapped to the selected Payment Types included within the plan.
The user must make sure that the Payment Type has a Limit Code linked to it by checking the Limit Definition table in the Bank Settings. If it does not exist, the user must add
it.

Please refer to the Limit Code Definition section (located at Bank Settings) for more information on the Limits Definition process.

Step 3
After selecting the Limit Code, the user must then configure the limit definitions. If a Limit Template is available, the user can select it from the list and load the limit definition
that is already predefined.
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 161 of 252
 162

P. Subscriber Fees

This stage involves configuring the fees that the subscriber will be charged for the plan.

Step 1
Enter the Joining Fee – this fee is applied to subscribers who activate the service for the first time. This will be a one-time only fee.

Step 2
Enter the Monthly Fee

Step 3
Enter the Yearly Fee

Step 4
Enter the Monthly Fee Waiver – if applicable

After saving all the information from all three stages, the plan will be created and added to the system. The DIB user can then link the plan to different customer
segmentations.
 163

Templates

This section will detail the templates that DIB bank users can create for pricing and limits. These templates can then
be linked to different plans.

The templates that can be created are:

 Pricing
 Limits

Q. Pricing Template

DIB bank users can create and link pricing templates to different plans. Pricing templates are created to provide a
default pricing for all the different payment types available.

The construction of the pricing template is based on the Billing Type.

Property Description
Billing type The payment type group that the payment type belongs to

When filling in the pricing template, the DIB bank user must configure the pricing for the different account types
available within each Billing Type.

Example:
 Billing Type: Postpaid
 Pricing – to be filled for each account type:
o CASA
o Wallet SVA
o Credit Card
o Walaa

Billing type

The different Billing types available in the system are:

Billing type
Web Payments
ATM Payments
POS
Postpaid Bills
Postpaid Blind
Prepaid with Quotation
Top Up
Vouchers
Gift Cards
Subscription

Web Payments
The web payment service enables subscribers to conduct purchases online through the PinPay Wallet Platform
payment gateway. Purchases are made by generating an OTP on the PinPay Wallet app and entering it into the
biller’s website to confirm the payment.
 Dubai Islamic Bank-IT Department

ATM Payments
The ATM payment service enables subscribers to conduct purchases through any DIB ATM.

POS
The POS payment service enables subscribers to conduct purchases through any of DIB’s POS. The subscriber would
have to generate an OTP on the Wallet PinPay app. This OTP would have to be entered into the POS in order to
complete the transaction.

Postpaid Bills
This service enables subscribers to inquire their postpaid bills on the PinPay Wallet app. Once the bill is presented,
subscribers can settle the bill on the app.

Postpaid Blind
This service enables subscribers to pay their postpaid bills on the PinPay Wallet app by entering the bill reference
number and the amount they wish to pay. There is no bill inquiry stage; the subscriber pays his bill without the bill
amount displayed.

Prepaid with Quotation

This service enables subscribers to conduct a purchase through the PinPay Wallet app by initially inquiring the
product’s price. Once the price is presented, the subscriber can conduct the purchase.

Top Up
This service enables subscribers to purchase a direct recharge product through the PinPay Wallet app. These
products automatically top-up the subscriber’s account.

Vouchers
This service enables subscribers to purchase vouchers through the PinPay Wallet app.

Gift Cards
This service enables subscribers to purchase gift cards through the WalletPinPay app.

Subscriptions
This service enables subscribers to purchase subscriptions through the WalletPinPay app.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 164 of
252
 Dubai Islamic Bank-IT Department

New Plan Template Workflow

Step 1
User selects on Templates, then on Pricing.

Step 2
User must select the Billing type he wishes to create the pricing template for.

Step 3
User must enter the Template’s Name and Description. User then clicks on Add Template.

Step 4
User must enter the pricing for each Account Type:
 CASA
 Wallet SVA
 Credit Card
 Walaa

The pricing for each account type is based on the structure mentioned in the section: (Account Type Pricing).

Step 4
After configuring the pricing for each account type, the user can save the price template. He can then link the pricing
template to a plan.

Note that the user can create multiple templates for the same Billing Type.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 165 of
252
166
 167

R. Limit Template

DIB bank users can create and link limit templates to different plans. Limit templates are created to provide a default
limit definition for each available account type.

New Limit Template Workflow

Step 1
User enters Templates, then enters the Limits section

Step 2
User selects the Account Type that he wishes to create the template for.

Step 3
User enters the Name and Description of the template.

Step 4
 User enters the following information:

Parameters Description
Daily Limit Amount The daily limit in transaction amount
Monthly Limit Amount The monthly limit in transaction amount
Daily Transaction Count The daily limit in transaction count
Monthly Transaction Count The monthly limit in transaction count
Max Transaction Amount The maximum transaction amount allowed
Currency ID Currency ID of the limit group

 Select whether the limit is:

o Sender
o General
o Affects Global
 168

Figure 25 - Subscriber Plan Creation Workflow Figure 2127 - Subscriber Plan Creation Workflow

Customer
Subscriber Fees Plan A Segmentation

Select which Limit

Select which Account
Codes to include in
CASA Wallet SVA Credit Card Walaa Types to include in
the Plan, per
the Plan
Account Type

Select which
Billing Type
Billing Types to
Postpaid
include

All Payment types linked to Billing Types loaded

Pricing Template
loads predefined
Payment Types Payment Types pricing
Etisalat Postpaid Bill GEMS Tuition Fees
If unavailable,
create new

Pricing only
applicable to
Pricing: Pricing:
allowed Account - CASA: 25 AED - CASA: 25 AED
Types in the Plan - Wallet SVA: 2% - Wallet SVA: 2%
 169

Plan Configuration Queue

When DIB bank users configure the different items in the plan, such as limits, fees etc. the request requires an
authorizer to approve the modifications. These changes are considered system changes.

Step 1
DIB bank user configures any component of a subscriber’s plan (limit, fee, etc.) and saves it. The change request is
sent to the Plan Configuration Queue.

Step 2
An authorizer will access the Plan Configuration Queue part of the portal to approve the plan configuration changes
made.
 Dubai Islamic Bank-IT Department

Figure 26 - Plan Configuration Workflow Figure 2228 - Plan Configuration Workflow

Plan Configuration
Plan Request Plan Approval

User selects on Plan

Management

User either modifies

an existing plan or
creates a new one

User selects on save

and the request is
submitted
3

The Plan Request is

sent to the Plan
User views Plan
Configuration Queue 4
request
and is in pending
approval status
5

User approves Plan

request

The new plan or

existing plan changes
have been executed
Phase

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 170 of
252
 Dubai Islamic Bank-IT Department

P2P Transactions

DIB bank users will be able to perform P2P transactions on the bank portal on behalf of the subscriber. In order to do
so, the user must enter the subscriber’s mobile number, the recipient’s mobile number and the amount to send.

The user can also add a note into the transaction.

Note that this process is a dual authentication one and requires an authorizer to confirm the transaction.

P2P Transaction Queue

All P2P transactions conducted by the DIB bank user will require an authorizer to approve and execute the transaction.

All pending P2P transactions are logged into this queue. An authorizer must select to confirm the P2P transfer before
the transaction can be complete.

Refunds Queue

All refund requests initiated by a DIB bank user are logged into this queue.

An authorizer must select to confirm the refunds transaction request before the refund can be complete.

Unload SVA Queue

All unload SVA requests initiated by a DIB Bank user are logged into this queue.

An authorizer must select to confirm the unload SVA request before the transaction can be complete.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 171 of
252
 Dubai Islamic Bank-IT Department

Disputes Management

The disputes management section of the subscriber management segment of the bank portal will enable DIB bank
users to manage the following:

 Disputes Queue
 View Disputes History

Disputes Queue

The disputes queue holds all subscriber claims that were submitted and are still pending review. DIB bank users can
access this section of the bank portal to follow up with each individual claim.

As the Wallet PlatformPinPay user resolves each claim, he marks their statuses as closed. Closed claims are then
logged into the Disputes History section.

Disputes History

The disputes history section logs all closed subscriber claims along with the resolution action taken. The DIB bank
user can search for a specific claim by searching with any of the below criteria:

 Claim Type
 Transaction ID
 Subscriber Mobile Number
 Date and Time
 Merchant ID
 Payment Type Name
 Decision Taken

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 172 of
252
 Dubai Islamic Bank-IT Department

Reports

DIB bank users can generate and inquire the following reports:

Reports:
1. Customer information file data download report all customers information
2. SVA statement for a specific customer
3. Linked statement for specific customer
4. Linked account transaction history both for current linked or historical linked
5. Daily transactions activity
6. Customer profile as a report
7. Suspicious activity report – DIB to provide the parameter
8. SVA creation report (monthly/daily/yearly) per segment
9. Number of active SVA
10. Number of blocked SVA
11. Number of SVA per customer
12. SVA portfolio report (total number of SVA / balance) all per segment
13. SVA with balance above Xx / transactions above XXX
14. SVA performance
15. Agent settlement report

Inquiry
 Customer profile with complete changes history audit
 Transactions history with additional logs

Note that all reports will be in WYSWYG format and can be exported in the following formats:

 XLS
 Text
 CVS
 PDF

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 173 of
252
 Dubai Islamic Bank-IT Department

3. Biller Management
DIB bank users can onboard merchants and manage the different merchant features through this section of the Bank
Portal.

The main functionalities to be included in the Biller Management section are:

 Enrollment
 Enrollment Queue
 Inquire Biller
 Plan Management
 Plan Configuration Queue
 Cut-Offs
 Execute Manual Settlement
 Cut-Off and Manual Settlement Queue
 Refunds Queue
 Bank Account Queue
 Frequency Queue
 Disputes Management Queue
 Reports

Maker / Authorizer Activities

As mentioned previously in the Maker/ Authorizer section of the document, certain functionalities and activities that
are performed on the Bank Portal may require single or dual authentication to fully complete the function.

The matrix below therefore highlights the maker/authorizer activities that can be done in the Biller Management
section of the portal:

# SVA Activities Execution Queue

1 New Enrollment Dual Authentication Enrollment Queue
2 Execute Manual Settlement Dual Authentication Cut-Off and Manual Settlement
Queue
3 Debit Merchant on PinPay systemWallet Dual Authentication Refunds Queue
Platform for Refund or Net-Off Settlement
4 Change Bank Account for Merchant Credit Dual Authentication Bank Account Queue
5 Change Fee Structure Dual Authentication Plan Configuration Queue
6 Change Cut-off / Settlement Frequency Dual Authentication Frequency Queue
7 Block / Activate Merchant Single
8 Update Merchant Profile Single
9 Send Notification (Email / SMS) Single
N/A
10 Enable / Disable Merchant POS Single
11 Generate / Send adhoc computerized Single
statements

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 174 of
252
 Dubai Islamic Bank-IT Department

Enrollment

The biller onboarding process will require the biller to fill out a form and submit it to DIB. The DIB user will continue
the registration process from thefrom the Bank Portal web-interface. The biller will then be able to download an
onboarding SDK.

The following definitions should be noted:

SDK (Integration Kit)

PinPay Wallet platform will provide billers with an onboarding SDK. The onboarding SDK will enable the biller to enroll
himself by integrating the SDK into his system.

Note that both BPP and Web Checkout billers share the same SDK.

The SDK will expose the different functionalities that the merchant can perform, such as:

 Inquire Bill
 Pay Bill
 Check Payment
 View Reports (should only show if transaction has failed or successful)

Sandbox Environment
The sandbox environment is the testing environment that certain billers will be activated into after enrollment.
These billers must be able to test their full service functionalities in this environment in order to troubleshoot and
resolve any issues that may arise.

This environment will accommodate the different testing parameters, data and white labelled users to test the
biller’s functionalities with.

Once the testing cycle has been completed, the biller will be activated into the production/live environment.

Activating Biller to Production

This process is still being developed and will be shared with DIB once ready.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 175 of
252
 Dubai Islamic Bank-IT Department

Onboarding Billers (Online Merchant Case)

In order to onboard merchants, both the BDM and PinPay Wallet Platform team will be involved in the acquisition
process on behalf of DIB. After the preliminary negotiations of the service requirements and service level
agreements have been completed, the merchant would be required to fill in and sign an onboarding application
form.

The onboarding process is detailed below.

Step 1
Merchant fills in the application form providing his details, selecting the services and signing a services agreement.

Services to select:
 Bill Presentment (Online, Offline, Blind)
 Mobile POS Payments
 Web Checkout
 Catalog Listing and Sales
 Cash In/ Cash Out Services

Details to be filled as according to the required information provided by DIB.

Note that each service offered to the biller will have its own bill template available. DIB bank users can create and
customize each template in the Content Management section of the Bank Portal.

When completing the biller onboarding process on the Bank Portal web interface, the bank user can select the bill
templates that are consistent to the biller services selected.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 176 of
252
 177

Step 2
If the merchant is a DIB customer, he must provide his DIB credit account. If the merchant is not a DIB customer, he
must provide his IBAN.

Step 3
If the merchant is a DIB customer, the DIB bank user will enter the merchant’s CIF in order to fetch the merchant’s
information from Flex. The information is then automatically populated into the merchant’s application form.
 Dubai Islamic Bank-IT Department

Step 4
If the merchant is not a DIB customer, the DIB bank user will proceed to convert the merchant into a DIB customer by
entering the Merchant’s details into the Bank Portal in order to onboard the merchant into the system..

On the Bank Portal, the DIB Bank user selects to Add New Merchant and enters the merchant details as stated in the
provided Application Form.

Onboarding Details to Enter (General Info):

 Entity Details
o Merchant’s Full Name
o Merchant’s Preferred
o Merchant’s Country of Incorporation
o Merchant’s Date of Incorporation
o Merchant’s Nature of Account
o Upload Merchant Logo Formatted: Font: 12 pt

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 178 of
252
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 179 of
252
 Dubai Islamic Bank-IT Department

 Address and Contact Info

o Enter Merchant’s Care Name (If Applicable)
o Enter the Merchant’s Full Address

 Group Details
o Group Detail’s Full Name
o Group’s Nationality
o ID Name
o ID Number
o Business Description
o Trade License Number
o Select the Issuing Authority (Dubai, Abu Dhabi, Sharjah etc.)
o Select the Issuing Date
o Select the Issuing Expiry Date
o Select the Group’s Legal Constitution (Sole Proprietorship, LLC, Free Zone etc.)
o Select the Group’s Line of Business (F&B, Aviation, Transport, Telecommunication etc.)
o Select Account Type (Basic, Plus, Premium, Large Corporate etc.)
o Select a Category (Retail, Corporate, Staff etc.)
o Select a Segment (Normal, Mass, Salaried etc.)
o Enter the Business Segment (Financial Institutions, Home Finance, Contracting Finance etc.)
o Enter the SIC Code
o Enter Group’s Address and Contact Information

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 180 of
252
 Dubai Islamic Bank-IT Department

Step 5
After entering the Merchant’s general company details, the DIB Bank User would then be required to enter the
Merchant Services information.

 Service Information
o Select Service Type – in this case for this example, the DIB Bank User selects the Online service type
(Postpaid bill online, Voucher online etc.) Selecting the Service Type will reveal the template required
for this particular service type.
o Enter Service Name
o Enter the Service Description
o Select Service Category
o Select the Service Limit Group
o Select a Currency
o Select the Button Name (this is the name that will appear on the app)
o Select the Sorting Order

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 181 of
252
 Dubai Islamic Bank-IT Department

 Identificators
o Enter the Identification Option Name
o Enter an Identificator – Bank user can select to add more in case merchant requires more (this refers
to information

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 182 of
252
 Dubai Islamic Bank-IT Department

 Product Information – In case the Merchant has selected a Service Type that has Vouchers, this section will
be displayed on the Portal.
o Enter the Product Name
o Enter the Product Description
o Enter the Product Amount
o Select the Amount Type
o Select the Sorting Order
o Enter the Voucher Presentment Label
o Enter the Voucher Presentment Description

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 183 of
252
 Dubai Islamic Bank-IT Department

 Bill Presentment Information – In case the Merchant provides Postpaid Bill services, he can select what Bill
Info he wishes to display to his customers
o Select the Bill Information to be displayed – from drop-down list available
 Bill Cycle Day
 Bill Amount
 Bill Status
 Bill Issue Date
 Etc.
o Select the Subscriber Information to be displayed – from drop-down list available
 Subscriber Name
 Subscriber Email
 Subscriber Phone Number
 Etc.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 184 of
252
 Dubai Islamic Bank-IT Department

The user will then link the merchant to a plan with a fee structure for the fees on receiver already set. He will also be
able to select the different bill upload templates for the biller (for file uploads), if required.

After confirming the application, the user will submit the enrollment to be reviewed for approval by an authorizer.
The merchant onboarding request is sent to the Enrollment Queue.

Step 6
After saving all the entered information, the Merchant Creation Request will be logged in a Queue to be reviewed and
approved/rejected by an Authorizer.

An authorizer will access the Enrollment Queue in order to verify the details submitted and will activate the merchant
into the system after validation. Compliance must also approve the Merchant.

Once the merchant has been approved, the DIB Bank user can link the merchant to a plan with a fee structure for the
fees on receiver, fees for receiver and so on. The fee structure for the merchant is detailed below:

Step 76
A welcome email is sent to the approved Merchant with the following:
 Merchant Portal link
 Merchant Credentials to log into the Portal
 Onboarding SDK
 Merchant Portal User Guide and Training Manual

After validation, the merchant will automatically move into the sandbox environment and must undergo testing before
being moved to production.

In some cases, the merchant will automatically move into the production environment without passing through the
sandbox (for web checkouts, online integrations).

Step 87 – Onboarding SDK

The Merchant can log into his account in the Merchant Portal to setup his profile information and details etc. He
must also integrate the Onboarding SDK in order to enable his services.

After setting up his account and integrating the SDK, a Merchant Setup Request is sent to DIB for an authorizer to
approve the request.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 185 of
252
 Dubai Islamic Bank-IT Department

Step 9 – Sandbox Environment

If the Merchant Setup Request is approved, the Merchant will be activated into the Sandbox Environment for
testing. The Merchant would need to test all functionalities of his service, ensure they are successful, before DIB
approves it.

In some cases, the merchant will automatically move into the production environment without passing through the
sandbox (for web checkouts, online integrations).

Step 10 – Production Environment

DIB system will be able to monitor the testing process performed by the Merchant. If the testing is successful, the
Merchant will be moved to the Production Environment.

A welcome pack will be sent to the merchant and will contain various guidelines and training documents once the
onboarding process is complete.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 186 of
252
 187

Figure 27 - Merchant Onboarding Figure 2329 - Merchant Onboarding

Merchant Onboarding
Phase

Merchant fills in
Application
Merchant

Form

Merchant
1 DIB user creates
2. No provides his 3. merchant s CIF
4.
IBAN

Merchant onboarding
Bank Portal

Is the merchant a request sent to

DIB Customer? Merchant Enrollment
Queue

Merchant Populates the

DIB user enters
2. Yes provides his DIB 3. merchant s CIF
application 6.
Credit Account form

4.
DIB System

Fetches the
(Flex)

merchant 5.
information
 188

Enrollment Queue

All merchant onboarding requests will be logged in the Merchant Enrollment Queue for an authorizer to review and
approve.

Once approved, the merchant is transferred into the sandbox environment for testing before being moved to
production.

Figure 28- Merchant Enrollment Queue Figure 2430 - Merchant Enrollment Queue

Merchant Enrollment Queue

Request Approval

User submits the Request is sent to the

Merchant Enrollment 1 Merchant Enrollment
Request Queue
2
User reviews the
request and selects
to move merchant to
Sandbox
Environment

User confirms the

request

The merchant is
moved to the test
Phase

environment
 Dubai Islamic Bank-IT Department

Inquire Biller

DIB bank users will inquire a biller in order to view his profile and transaction information. The user can then investigate
and resolve any issues or complaints that are raised from the biller.

Inquire Process

The DIB bank user must search for an existing biller in order to perform subscriber specific functions. To do so, he must
first enter the biller’s search information.

Step 1
DIB bank user accesses the Inquire Biller section of the portal and must enter one or all of the following:

# Search Criteria
1 Biller Name
2 Biller ID

Step 2
When the search results are displayed, the bank user can then select the biller from the list provided.

# Name Merchant ID Status Action

1 Emaar Real Estate 1121 Active View Profile
2 Etisalat 1122 Blocked View Profile
3 RTA 1123 Cancelled View Profile

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 189 of
252
 190

Biller Dashboard

DIB Bank users can perform a number of activities on the biller’s profile after inquiring it. Each functionality is briefly
described below.

S. Profile Information

The biller’s key profile information are displayed in a table, including his name, Biller ID, status and plan.

T. View Additional Info

The user can select to view additional information, which would result in a broader overview of the biller’s profile

U. Edit
The user can also select to edit the biller’s information.

V. Profile Alerts
The profile alert table will display the biller’s last 5 transactions conducted. The transactions displayed are prioritized
according to whether the transaction was successful or not – failed transactions will show first to provide the user with
quicker access in the resolution process.

The user can select each transaction in order to get a more detailed overview of it.

W. Block/Activate
Enables the DIB bank user to block a biller and reactivate a blocked biller.

 Blocking a biller will automatically disable it from functioning and prevent subscribers from performing any
transactions for this specific merchant.
 Activating a biller will automatically enable it and return it back to the active state. The biller’s services will
then be available to subscribers to perform transactions for this specific merchant.

X. Cancel
Enables the DIB bank user to cancel a biller’s PinPay Wallet membership.

The above processes follow the same workflow as found in the subscriber’s management section.
 Dubai Islamic Bank-IT Department

Accounts

DIB bank users can manage the biller’s bank account details in the Accounts tab of the Biller Dashboard.

Y. Modifying Account Details

Modifying the account details of the biller requires an authorization in order to execute the process. When modifying
the account details, the user must initially submit a Bank Account change request and have it approved.

All submitted modification requests are logged in the Bank Account Queue section of the portal for further review.

Z. Change Settlement Frequency

DIB bank users can modify the merchant’s settlement frequency details. This also requires a dual authentication
process to execute. When modifying the settlement frequency, the user must initially submit a Settlement
Frequency change request and have it approved.

All submitted modification requests are logged in the Frequency Queue section of the portal for further review.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 191 of
252
 Dubai Islamic Bank-IT Department

Billing Types

DIB bank users can enable and disable the Billing Types, including the merchant POS (M-POS) service. This function
will be located in the Billing Types tab.

Therefore, DIB bank users can at any time, enable or disable the POS billing type or any other Billing Type if required.

Payment Types

DIB bank users can change a merchant’s fee structure in the Payment Types tab.

Modifying the fee structure will require a dual authentication process in order to execute. Therefore all modification
requests made to the fee structure will be logged in the Plan Configuration Queue.

An authorizer with the authority to execute a fee modification will access the Plan Configuration Queue and either
approve or reject the request.

The following feature should be noted:

 Waiver mechanism for partial waiver

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 192 of
252
 Dubai Islamic Bank-IT Department

Transaction History

DIB bank users can view the history logs of all the transactions conducted for the specific merchant. The user can
search by date, time, account type, payment type name and transaction status.

The user can perform the following functions in the subscriber’s transaction history page:

AA.Submit Claim
Select to submit a claim for any of the transactions displayed if required.

BB. Refund Transaction Request

Some claims may require a refund request and approval process.

Both of the above processes follow the same workflow as found in the subscriber’s management section.

Send Notifications / Claims

This process follows the same workflow as found in the subscriber’s management section.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 193 of
252
 194

Plan Management

DIB bank users can create plans (pricing templates) in the Plans Management section of the Bank Biller Portal. A plan is predefined template that details the fees charged to
the biller.

DIB bank users can then link created plans to providers. These providers will then have a predefined pricing template (as available in the plan) linked to it.

Plan Creation Workflow

To create a plan, DIB bank users must follow 2 stages:

Stage Description
User must enter general information regarding the plan’s
Plan Definition
definition
 User must configure the subscription fee charged to the
biller for each billing type
Plan Billing types  User must configure the limits for each billing type
 User can configure the pricing for all payment types with
a single, default pricing

Each stage is elaborated below.

 Dubai Islamic Bank-IT Department

CC. Plan Definition Details

Step 1
Users enter the Plan Name and Description

Step 2
User selects whether the plan is active or inactive before proceeding to the next step

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 195 of 252
 196

DD. Plan billing types

Step 1
User must fill in the limits for each billing type

Step 2
User must enter the subscription fee for each billing type:
 Enablement Fee
 Monthly Fee
 Yearly Fee
 Maintenance Fee
 197

Step 3
If the user wants to enable all payment types that are linked to the billing type with a uniform pricing (fee on receiver), he should fill in the Pricing section also detailed in this
screen (note that it is not shown in the screenshot below).

Note that the pricing configured applies to all account types. Please refer to the Account Type Pricing section for details on the pricing components.
 198

EE. Limits
The user must then define the different limits for each Billing type. There are 2 different types of limits available:

 Alert Limits
 Effective Limits

Alert Limits
If these limits are exceeded, DIB is alerted but the biller’s operations are not blocked. DIB can then notify the biller that he has surpassed his limits. Alert limits apply to:

 Daily Count – number of transactions per day

 Daily Amount – amount (in Dirhams) per day
 Monthly Amount – amount (in Dirhams) per month

Effective Limits
If these limits are exceeded, DIB is alerted and the biller’s operations are blocked. Subscribers will not be able to conduct transactions.

 Min Transaction Amount – the minimum amount (in Dirhams) allowed per transaction
 Max Transaction Amount – the maximum amount (in Dirhams) allowed per transaction
 199

Plan Configuration Queue

DIB bank users will be able to authorize all configurations made to the plan including changes made to the fee
structure. These type of requests are logged in the Plan Configuration Queue for authorizers to review and approve.

This process follows the same workflow as found in the subscriber’s management section.

Mobile M-POS Management

This section of the Bank Portal will enable DIB bank users to manage the M-POS terminals provided to billers. Users
can perform the following functions:

 Assign Terminals to Billers

 Activate / Disable Terminals
 More functionalities/features to be added upon discussion with DIB

Assigning Terminals to Billers

If a biller requests the M-POS service, the DIB bank user can link the biller to an M-POS terminal. If the biller requests
multiple terminals, the bank user will be able to link the biller to multiple terminals.

Each terminal will have its own unique ID that the biller will receive in order to activate his terminal. Once the ID has
been entered into the terminal, it would activate the PinPay Wallet M-POS app for the biller to begin conducting
purchases.
Note that this activation workflow will still need to be discussed with DIB to finalize it.

Activate / Disable Terminals

DIB bank users can view and manage the number of terminals linked to each biller and their statuses (active,
disabled). The bank user can disable and reactivate terminals.

Cut-Offs

DIB bank users will have an overview on the issuing and acquiring transactions occurring in the system by accessing
the Cut-Off Period, Acquiring Transactions and Issuing Transactions sections of the portal.

The recon and settlement process will allow the user to prepare the transaction file (Batch File) that he would use to
settle with the providers.

The Reconciliation and Settlement section is therefore divided into three sections that are displayed in the portal:

 Cut Off Period

 Acquiring Transactions
 Issuing Transactions
 Dubai Islamic Bank-IT Department

Cut-Off Workflow

The DIB bank user will initially need to cut off the current period in order to prepare the transactions that were
conducted.

All transactions conducted during a certain period are grouped into a sequence number. When the DIB bank user
wishes to cut off the period, he would be ending the current period (example sequence 1). As he ended the previous
period, a new period will immediately begin (sequence 2).

The user can then view the details of all the transactions that were performed during the previous periods (sequence
1) and begin preparing those transactions for processing.

DIB bank users can change the automated cut-off frequencies.

Step 1
User clicks on the Get Current Period button in order to view the current period. This will also detail the start date and
time that current period was started on.

Step 2
User clicks on the Cut-Off Period button in order to cut off the current period.

All transactions that were conducted during the previous period (and are therefore linked to the previous sequence)
will now be compiled for the user to begin processing.

Step 3
The period that was cut off will appear in the Open Periods table. All periods that were cut off and contain transactions
that were not yet processed will appear in this table.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 200 of
252
201
 202

Execute Manual Settlement

DIB bank users can execute a manual settlement. This user must initially perform a cut off before being able to process
and execute a settlement.

Note that the manual settlement process requires a dual execution before being fully completed.

Acquiring Transactions

After the DIB bank user has performed any cut offs, he can then start making the required preparations to process the
acquiring transactions that were conducted during any selected period that was cut off.

This section will therefore detail the process in two parts:

A. Import Files
B. Process & Export Files

A. Import Files

To prepare the transaction file for processing, the user would have to initially import the transaction file for the
selected period and run a check to validate the payments that subscribers have conducted. Ultimately, the user must
ensure that the transaction data (including the totals) available at the bank matches that data available at PinPayWallet
Platform.

If Data Discrepancy Exists

If the user notices any inconsistencies in the data coming from both the bank and Wallet PlatformPinPay’s end, he
would need to request a transaction detail file from Wallet PlatformPinPay. Data discrepancies can occur if a timeout
or connection failure occurs between Wallet PlatformPinPay and the bank, resulting with incomplete records on the
bank’s end.

In order to ensure that the bank has the complete list of transactions, the bank user would need to request a file from
Wallet PlatformPinPay. This file will contain all transactions conducted during the period.

Validated Transaction Details

Once the transaction details are validated, the user will then be able to create the required batch files for acquiring
parties. The batch files will contain the list of transactions and their details that the user must export in order to settle
with the bank’s providers.
 203

Import Files Workflow

Step 1
User selects on the period he wants then clicks on the Import Files button.

Step 2
User will be taken to a table that will display the sequence details, including the start and end time.

Step 3
User clicks on the Calculate Inflight Totals button in order to load a summary of all the transactions conducted during the selected period. The transaction data that is received
here is loaded from the bank’s end.
 Dubai Islamic Bank-IT Department

The details section will display the following:

 First Transaction ID
 Last Transaction ID
 Total Transactions Count
 Total Transactions Credit Count – total number of refunds made
 Total Transactions Debit Count
 Currency
 Total Credit Amount – total amount of refunds made
 Total Debit Amount – the total amount debited during the selected period. This is the total product amount (excluding fees).

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 204 of 252
 Dubai Islamic Bank-IT Department

Step 4
User clicks on the Calculate Acquiring Totals button in order to load a summary of all transactions conducted during the selected period. The transaction data that is received

here is loaded from PinPay’s Wallet platform’s end. The DIB bank user would load this data in order to ensure that the banks’ details and PinPay’s Wallet Platform match,

Step 5
The user can click on the Compare Totals button in order to run an automated comparison check between the data loaded from the Inflight and Acquiring totals.

If the status results in Validated, this would mean that the totals at the bank and at PinPay Wallet platform match and there are no discrepancies available. At this point, the
acquiring transactions files will be ready for processing.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 205 of 252
 Dubai Islamic Bank-IT Department

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 206 of 252
 Dubai Islamic Bank-IT Department

Step 6 – If a discrepancy exists:

If the transaction details at the bank and at PinPay Wallet Platform are inconsistent, the user must select on the Request File button in order to retrieve the transaction file
from PinPayWallet Platform.

Afterwards, the user must click on the Check File button to run an automated checking process. This function will check whether both totals match (inflight and acquiring).

If the result is False, the DIB bank user can select on the Import File button to use the PinPay Wallet Platform transaction file to replace the existing transaction records on
the bank’s end.

Step 7
After comparing the totals, the user would then need to click on the Go Back button in order to return to the previous screen. At this point, the acquiring transaction details
have been imported (from either the bank’s end or PinPay’s) and ready to be processed.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 207 of 252
 208

B. Process & Export Files

After confirming the transaction totals, the DIB bank user can then process the file. During this stage, the file will be sent to PinPay Wallet Platform in order to perform two
tasks:

1. Record accounting information

2. Flag each transaction with the Batch number

Record Accounting Information

Wallet PlatformPinPay will ensure that all the transactions conducted include the proper accounting numbers with it. These numbers refer to the RBS Account, Source
Account, Fees on Receiver Account and Fees for Receiver Account.

Flag Each Transaction

At the same time, PinPay will flag each transaction with the Batch Number that the transactions would be linked to.

After processing, the user can export the batch file and view the list of transactions and their details. The transaction details will include the transaction classes available in
the batch file:

1. Payments

2. Forced Payments – these are payments that have been forced due to an exception that occurred with the provider.

 When the exception occurs and the payment posting is forced within the same period, the DIB bank user will only need to request the file from Wallet
Platform PinPay (as mentioned in the Import File section) and use the updated file for settlement.

 When the exception occurs and the payment posting that is forced is not during the same period of the cut off, it will be available in the next period. The
forced payment transaction entry will be recorded separately in the settlement batch file.

3. Refund
 Dubai Islamic Bank-IT Department

Process & Export Files Workflow

Step 1
User selects the file(s) he wishes to process from the table. He then clicks on the Process Files button. After doing so, the information will temporarily be displayed in the
Process Details table.

As the user selected the Process Files button, the abovementioned functions have occurred (Record Account Info and Batch Flagging). The Process Details table will
therefore display the Batch Number that the transactions are linked to.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 209 of 252
 Dubai Islamic Bank-IT Department

Step 2

Once the file(s) have completed processing, the user can select on the Export Files button on the menu in order to head towards the Export Files section.

The table will display the batch file details, including files which have been processed or are still processing. Step 3
The user can select the batch he is interested in exporting before selecting the Export Files button. Doing so will export the file for the user to view and use for settlement
with the respective providers.

The exported file will contain the following transaction details:

 Source Account Number

ITPMO-INI-002 Version 1.2, June 2015
Controlled Document For Internal Use Only Page 210 of 252
 Dubai Islamic Bank-IT Department

 Destination Account Number

 Total Amount debited (Total Amount – Fees on Receiver + Fees For Receiver)
 Total Fees debited (Fees on Sender + Fees on Receiver)
 Transaction Date
 Transaction ID
 If the transactions are consolidated – they will appear as one entry (one for the amount and one for the fees)

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 211 of 252
 212

Issuing Transactions

This section will provide DIB bank users with the issuing transaction information for each period. It is important to
note that the details will not be displayed unless the user has already processed the file for the period (please refer to
the Process and Export section for more details on this).

The user can view the transactions conducted by subscribers on each Account Type, per period and per batch. To do
so, the user must first:

 Import the Files

 Export the Files
 213

Import & Export Files Workflow

Step 1
User selects the file(s) he wishes to process from the table. He then clicks on the Process Files button. After doing so, the information will temporarily be displayed in the
Process Details table.
 Dubai Islamic Bank-IT Department

Step 2
Once the file(s) have completed processing, the user can select on the Export Files button on the menu in order to head towards the Export Files section.

The table will display the batch file details, including files which have been processed or are still processing.

Step 3
The user can select the batch he is interested in exporting before selecting the Export Files button. Doing so will export the file for the user to view.

The exported file will contain the following transaction details:

 Source Account Number

 Destination Account Number
 Total Amount debited (Total Amount + Fees on Sender + Fees for Receiver)
 Transaction Date
 Transaction ID

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 214 of 252
 215

Cut-Off and Manual Settlement Queue

Any modification requests made to the cut-off frequency will be logged in this queue for authorizers to approve.

All manual settlement requests conducted will also be logged in this queue and would require an authorizer to confirm
and approve the request.
 Dubai Islamic Bank-IT Department

Disputes Management Queue

The disputes management queue holds all merchant claims that were submitted by DIB bank users and by billers
themselves. Users can access this section of the bank portal to follow up with each individual claim.

As the user resolves each claim, he marks their statuses as closed.

Refunds Queue

All refund requests initiated by a DIB bank user will be logged in the Refunds Queue for a Wallet PlatformPinPay user
to review.

Only the Wallet PlatformPinPay user can in this case confirm a refund request.

Duplicate Transactions
In case of a duplicate transaction, Wallet PlatformPinPay will have to get an approval from the biller before executing
a refund.

Bank Account Queue

All Bank Account modification requests submitted by a DIB bank user will be logged in the Bank Account Queue for
further review.

An authorizer will be required to confirm the modification.

Frequency Queue

All frequency modification requests made to the settlement or cut-off periods will be logged in the Frequency Queue
for further review.

An authorizer will be required to confirm the modification.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 216 of
252
 Dubai Islamic Bank-IT Department

Reports

The following are merchant reports and inquiry results:

Reports:
 Merchant information file
 Merchant Activity
 Merchant Settlement History
 Subscription Fees
 Merchant Dues
 Merchant cut off
 Merchant onboarding report (historical / status / source)

Inquiry Results:
 Merchant profile with all changes history audit
 Merchant transactions activity
 Secure notification / email
 Merchant performance

Operation Reports:
 Merchants transaction reports
 Disputes report (merchant/subscriber/bank)
 Merchant transactions recon upload
 Merchant statement of accounts
 Fee / Revenue reports for business partner share
 Fail transaction report single/all merchant

Note that all reports will be in WYSWYG format and can be exported in the following formats:

 XLS
 Text
 CVS
 PDF

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 217 of
252
 Dubai Islamic Bank-IT Department

4. Content Management
DIB bank users can access the Content Management section of the bank portal in order to perform the following
activities:

 Publishing in-app banners

 Offers and Deals – through QubifyDeals and offers portal
 Notification Templates
 Bill Upload Templates

Publishing in-app Banners

Users can publish informative and promotional banners on the PinPay Wallet app through this section of the portal.
The user must enter the Payment Type name (biller’s service) in order to link the banner to the service.

When subscribers select the banner on the app, it will redirect the subscriber to the specific payment type screen.

Note that this feature will not be available in phase 1. It will be available in phase 2.

Publishing Biller Logos

Users can publish biller logos that appear on the PinPay Wallet app through this section of the portal.

Offers/ Deals and Catalogs – Qubify Platform

DIB bank users and billers can create catalogs, offers, deals and publish them through the Qubify Deals and offers
platform. All publish requests coming from billers will undergo a revision process before being published to ensure the
content standards.

It will therefore be a dual authentication process.

Users will also be able view analytics of all subscriber actions done on the app through the Qubify Deals and offers
platform.

Note that the Qubify Deals and offers platform will not be available in phase 1. It will be available in phase 2.

Notification Templates
DIB bank users can define template definitions for each of the following:

 Notification Channel (email, SMS and app notifications)

 Notification Type (Registration, Payments, Disputes etc.)
 Target Segment (Per Plan)

For email, should mention whether to include attachments.

Bill Upload Templates

DIB bank users can define bill template definitions on behalf of billers based on the biller requirements and on what
fields are allowed and available on the platform.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 218 of
252
 Dubai Islamic Bank-IT Department

Note that each service category (real-time, upload bills, blind payments) would have its own template.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 219 of
252
 Dubai Islamic Bank-IT Department

5. Notification Management
DIB bank users can send notifications to any subscriber and merchant through the notifications section of the bank
portal.

 Users can use notification templates defined in the content management section to send notifications to
their subscribers or their billers.

 Notifications can be sent as:

o App notification – this can be:

 General
 Targeted
 Geo-fence
 Beacon
o Email
o SMS

 Scheduling feature to enable DIB bank users to schedule the launching of different notifications

 Subscribers can select whether to disable or enable specific notifications, and on which channels.

Note that certain notifications (Geo-fence & Beacon) will not be available in Phase 1.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 220 of
252
 Dubai Islamic Bank-IT Department

Notification List

Below are the different notifications that the system can send out to subscribers. Note that more notifications can be
added upon request.

# Description Email SMS App Notification

1 Email Verification Y
2 Successful Bill Payment with Payment Option Y
3 Successful Postpaid Bill Payment Y
4 Successful Postpaid Blind Bill Payment Y
5 Successful Direct Recharge Transaction Y
6 Successful Voucher Transaction Y
7 Generic Failing Transaction Y Y Y
8 P2P Outgoing Accepted Y Y
9 P2P Incoming Pending Y Y
10 P2P Outgoing Pending Y Y
11 P2P Outgoing Expired Y Y
12 P2P Incoming Execution Fail Y Y
13 P2P Outgoing Execution Fail Y Y
14 Points Earned Y
15 P2P Incoming Rejected Y Y
16 P2P Outgoing Rejected Y Y
17 P2P Incoming Accepted Y Y
18 P2P Incoming Expired Y Y
19 Register Mobile Y Y
20 P2P Incoming Pending (No Profile) Y Y
21 Payment Executed for POS Y
22 Payment Failed General Error for POS Y
23 Payment Failed Invalid OTP for POS Y
24 Payment Failed Invalid Mobile Number for POS Y
25 Payment Failed for Insufficient Fund for POS Y
26 Payment Failed Limit Reached for POS Y
27 Payment Reversal for POS Y
28 Payment Executed for ATM Y
29 Payment Failed Invalid OTP for ATM Y
30 Payment Failed General Error for ATM Y
31 Payment Failed Limit Reached for ATM Y
32 Payment Failed for Insufficient Fund for ATM Y
33 Payment Failed Invalid Mobile Number for ATM Y
34 Payment Reversal for ATM Y
35 Payment Executed for Web Payment Y
36 Payment Failed General Error for Web Payment Y
37 Payment Failed Invalid OTP for Web Payment Y
38 Payment Failed Invalid Mobile Number for Web Payment Y
39 Payment Failed for Insufficient Fund for Web Payment Y
40 Payment Failed Limit Reached for Web Payment Y
41 Payment Reversal for Web Payment Y
42 Bank Med Youth Enrollment (Bank Med specific marketing) Y

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 221 of
252
 Dubai Islamic Bank-IT Department

43 Voucher recharge Failed Y

44 Welcome Message with Instruction to complete KYC Y Y
45 Acknowledgement to be sent to customer for successful Add
Y Y
DIB
46 Acknowledgement to be sent to customer for KYC completion Y Y
47 Acknowledgement that Transaction is in Progress Y Y
48 Acknowledgement that Name screening failed Y Y
49 Acknowledgement that KYC has failed Y Y
50 Dispute Handled and Closed (include dispute request ID) Y Y
51 Dispute Decision Y Y
52 Remit to ATM expiry Y

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 222 of
252
 Dubai Islamic Bank-IT Department

6. Bank Settings
The Bank Settings section of the Member Center will enable DIB users to configure different predefined settings,
such as:

 Limit Code Definitions

 Segment Definition
 Services/Segment/Pricing mapping

Limit Code Definitions

This section will display a list of all available Payment Types and the Limit Codes mapped to them.

DIB bank users must link their Payment Types to the Limit Code definition that is available in the Plan. To do so, the
DIB bank user must manually enter the following information in the table:

 Add New Record

 Enter Payment Type ID
 Enter Payment Type Name
 Enter the Limit Code – this is the code that is already linked to the Payment Type

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 223 of
252
 Dubai Islamic Bank-IT Department

Risk Management
The following section will detail PinPay’s Wallet’s Platform risk management system that is currently in place.

Risk Scoring
PinPay Wallet Platform has multiple risk scoring systems in place that are implemented for the occurrences mentioned
below. Risks are monitored based on the user’s purchase history, transaction activity, timing of the transaction,
frequency and so on.

 Transaction risks: scoring system to monitor whether a transaction is considered high risked or not. High
risked transactions are instantly stopped and flagged for revision.

 Activity risks: dynamic scoring system to monitor user activity on the PinPay Wallet app. High risked activities
are flagged for revision.

 User onboarding risks: scoring system to monitor user onboarding process. If the user’s profile is considered
a high risk, the onboarding process instantly stops and the user is flagged. Someone will then review the user’s
onboarding application.

Technology and Software

The PinPay systemWallet Platform is protected by various technology and software that are used to monitor the
system and to prevent against fraudulent activities

Device Management
DIB bank users can control the user’s device through the device management section in the Bank Portal. The user can
remove devices (but he will not be able to re-add a device).

The subscriber can also manage his own devices through the device management section in the WalletPinPay app. He
can remove devices that his WalletPinPay app is linked to if he wishes to.

Function Management (Service Management)

DIB bank users can disable a service (biller service) on a system, plan and user level. Disabling a service will prevent
subscribers from performing that service on the WalletPinPay app until the DIB user has enabled it once again.

Note that for disabling a service on a user level, the Bank user must create a new plan that excludes the service(s) he
wishes to disable. The user must then link this plan to the subscriber.

Limit Management
The PinPay platformWallet Platform supports multiple limit types that can be controlled by the DIB bank user. These
limits extend to:
 Channel Limit – this is controlled and configured in the system itself (not through the Bank Portal).
 Merchant Limit
 Transaction Limit

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 224 of
252
 Dubai Islamic Bank-IT Department

 Daily Limit
 KYC Limit
 Segment Limit
 Linked Card/CASA Limit

User Management
DIB bank users can block and reactivate users on the Bank Portal if required. Blocked users will be unable to access
the WalletPinPay app and perform any transactions. Only once reactivated will he be able to resume standard Wallet
PinPay activities.

PinPay will be providing aA separate document for the Security and Risk Management system will be submitted.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 225 of
252
 Dubai Islamic Bank-IT Department

Compliance
There will be a list of compliance reports that DIB will provide PinPay. These reports will be added to the Bank Portal.

It should be noted that a full data dump will be sent to DIB compliance system daily after EOD.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 226 of
252
 227



Biller / Agent Portal

The purpose of this section of the BRD is to detail the business requirements for the Biller Portal interface that
PinPay will need to be provideding to Dubai Islamic Bank (DIB).

This document will therefore be illustrating the minimum business requirements for the Biller Portal that would be
available in the PinPay mobile Wallet platform for DIB.

The different interface and back-office components that will be outlined in this section of the BRD are:

Interface Components:

 Biller Portal
 Agent Portal
 Dubai Islamic Bank-IT Department

Biller Portal Features

This section of the document will detail the different services that DIB billers can perform on the Biller Portal:

 User Management
 Bill Management
o Create and Upload Bills
 Payments Reports
o View Bills (paid and outstanding)
o View Settlement history
o View Transaction Activity
 Manage Merchant profile
 Create and Publish Catalogs
 Create and Manage Disputes
 Approve Refunds
 Upload Receivable Invoices for Settlement from other B2B clients
 View Receivables and Payables
 Approve invoices for supplier payments
 View Reports

This section of the BRD will therefore describe each individual service offering in detail.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 228 of
252
 Dubai Islamic Bank-IT Department

7. User Management
The User Management section of the Bank Portal will enable billers to create new users, manage existing users and
assign user role privileges.

 User Management
 Role Management
 Privilege Management
 User Management Reports

User Management

This feature enables billers to add new users who will have access to the biller portal to perform specific functions.
The new user can have specific roles assigned to him.

When entering this section of the Biller Portal, billers can view a list of available users already added. They would be
able to:

 Edit – edit each user’s information, and request to reset the user’s password
 Activate / Deactivate – enable or disable the user’s status
 Add new user

Role Management

In this section, the biller admin can create new roles and define roles.

Privilege Management

The admin must select the functionalities allowed for each role. Depending on the role type, only the specific functions
that are allowed for each category can be selected.

User Management Reports

The following reports should be available:

 List of users stating their roles, functions and statuses

 Complete changes audit for users and groups

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 229 of
252
 Dubai Islamic Bank-IT Department

8. Bill Management

The Bill Management section will enable the biller to create and upload bills and make them available on
PinPayWallet Platform.

There are 2 ways of uploading the bills:

 Upload individual bills manually (Upload Individual Bills)

 Upload bills in bulk. This is done by uploading an excel or CSV file to the PinPay systemWallet Platform (Upload
Bills by File)

Note that at a later stage, subscribers will be notified that their bills are available for payment. This will not be
included in Phase 1.

Uploading Bills

Step 1
Biller user clicks on Bill Management section of the Biller Portal. Bills that are already uploaded are displayed in the
table.

Item Definition
Name The name of the bill uploaded
Product The product name
Version Version number of the upload
Successful Bill Number of successful bills uploaded – if uploaded in bulk, this number will display how many
Uploaded bills were successfully entered into the system
Failed Bill Uploads Number of failed bills uploaded – if uploaded in bulk, this number will display how many bills
failed to upload to the system
Total Records Total entered bills – this includes the summation of both successful and failed uploads
Time Stamp Date and time of the upload
Status Status of the uploaded bill could be:
 Posted – uploaded bills were submitted to the PinPay systemWallet Platform
 Created – bill was created but not yet submitted to the PinPay systemWallet
Platform
 Reconciled – posted bill has been reconciled

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 230 of
252
 231

Step 2
The biller user must then decide whether he wishes to upload bills individually, or in bulk.
 232

Upload Individual Bills Workflow

This process requires the biller to upload individual bills manually, one at a time. The biller would be required to fill in the following fields:

Item Definition
Version Number Version number of the upload
Date From Indicate the date range
Date To Indicate the date range
Product Name Select the Product
Step 1
Biller must enter the required fields displayed on the screen
 Dubai Islamic Bank-IT Department

Step 2
After entering the required fields, the biller must click on Save to proceed to the next screen

Step 3
Biller then enters the bill information:

Item Definition
Full Name Full name of the subscriber
Due Date Date that the bill is due
Student ID ID number of the subscriber
Bill Reference Bill Reference number of the subscriber
Filter 1
Customized filters that the biller can enter (example: Semesters)
Filter 2
Bill Amount Total bill amount due
Penalty Penalty fees
Currency Biller must specify the currency of the bill (USD or LBP)

Note that the data required to be entered depends on the product type.

For example, Tuition fees may require the subscriber to enter his Student ID, while Park Meter Fines may ask the subscriber to enter his License Plate.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 233 of 252
 Dubai Islamic Bank-IT Department

Step 4
After entering the required bill data, the biller clicks on save. The bill is then added to the portal (but not yet uploaded to the PinPay SystemWallet Platform).
The biller can add additional bills.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 234 of 252
 Dubai Islamic Bank-IT Department

Step 5
After saving the bill on the biller portal, the biller must now upload the bill to the PinPay SystemWallet Platform. He does so by selecting the bills availlable on the table by
enabling the checkboxes.

Bills that can be posted will have the status Created.

Step 6
Biller selects the bills he wishes to upload and clicks on Upload to PinPayWallet Platform.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 235 of 252
 236

Step 7
Biller confirms that he wants to upload the file

Step 8
Selected bills are then uplaoded to the PinPay systemWallet Platform. All uploaded bills will be available for subscribers to inquire and pay on the PinPay Wallet app.

Successfully uploaded bills will have the status Posted.

 237

Upload Bills in Bulk Workflow

Billers can upload bills in bulk by uploading a file template that includes the bills’ information.

Step 1
Biller clicks on Upload Bills by File

Step 2
Biller enters basic information regarding the file submission.

Item Definition
Version Number Version number of the upload. The number should be incremental, in case the biller might
want to upload more files with the same properties
Date From Indicate the date range
Date To Indicate the date range
Product Name Select the Product

Step 3
Biller downloads the Template from the portal and fills in the required bill information.

Step 4
Biller then uploads the file into the portal. Once the upload is complete, the PinPay systemWallet Platform will
automatically check and validate the uploaded file to make sure that all the records are correct.

The portal will then display a summary of successful and failed uploads for the biller’s consideration.
 Dubai Islamic Bank-IT Department

File Template Creation (Biller Upload) Workflow Formatted: Heading 4

Step 1
The Merchant accesses the Bill Management section on the Merchant Portal and selects “Upload Bills by File”.

Step 2
The Merchant then downloads the Bill Template. The following parameters are requested from the Merchant:

 Customer ID
 Association ID
 Mobile Number
 Email
 Full Name
 Bill Reference
 Sequence
 Amount
 Currency
 Issue Date
 Due Date
 Settlement Group
 Notes
 Last Payment Date
 Whether Partial Payment is allowed, if yes
o Min Payment Amount
o Partial Payment Percentage
o Whether Fractions are allowed
 Whether the Bill has a Penalty, if yes
o Whether Fractions are allowed
o Min Penalty
o Max Penalty
o Penalty Identifier
o Penalty Multiplier
 Filter ID 1
 Filter ID 2

Step 3
The Merchant fills in the Excel Sheet with the required information depending on the relevancy. The Merchant will
also be able to add/remove parameters from the Excel Sheet depending on its requirements and needs.

Step 4
The Merchant then uploads the file in the Merchant Portal in the Bill Management section – Upload Bills by file. The
file is received by the PinPay system and the data is validated. Invalid information is flagged for the Merchant to
modify.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 238 of
252
 Dubai Islamic Bank-IT Department

Step 5
Validated bill information will then be available on the PinPay system. Subscribers can now inquire and pay for their
bills.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 239 of
252
 240

Figure 2531 - Merchant File Template Creation Upload Formatted: Caption

Merchant Bill Upload with a File Template Field Code Changed

Phase

The Excel File Template will

Merchant

Access the Bill be downloaded with the

Start Management section requested Bill Parameters Fill in the Excel Sheet
on the Merchant Portal
Merchant Portal

Upload File onto

Select on Upload Bills Merchant Portal in the Merchant is notified of
by File and select on Bill Management – Invalid Data to be modified
Download Template Upload Bills by File
section

N
Wallet Platform

Data Validation Approved

Y
DIB Wallet

Bills are now available

on the App for payment End
by Subscribers

Report Output Input Data Bank Portal Input Update Utility Sub System Sub Process

Formatted: Caption
 241

9. My Provider Reports
The Payments Reports section of the biller portal displays different reports and statuses of the biller’s bills. The biller will be able to view reports for their paid and
outstanding bills, their settlement history and transaction activities.

Accessing My Payments Reports will display the following to the biller:

 A list of bills that have already been paid are displayed

 Today’s Payments – Biller can view all payments conducted on the current date
 Unsettled Payments – Billers can view all payments that need to be settled
 Settled Payments – Billers can view payments that have already been settled
 242

Upload Receivable Invoices

In case the biller has invoices from other B2B clients that are pending settlement, the biller can upload these invoices
directly on the biller portal interface.

These uploaded invoices will then enter a queue to be processed.

Approve Refunds

Billers can approve refunds for settled transactions.

 Dubai Islamic Bank-IT Department

Profile Management
Billers will be able to manage their own profiles in the Profile Management section. They would be able to do the
following:

 Change Password
 Change profile information

10. Create and Publish Catalogs

Billers will be able to create and publish catalogs for their products and services. The presentment of product catalogs,
offers and deals and other similar content will be discussed during the redesign of the PinPay Wallet app to align with
the engagement and interactive requirements set forth by DIB and PinPay.

Qubify Deals and offers Interface System

The Deals and offersQubify component will be responsible for the creation of the product/service catalog as well
as the pushing of the offers and deals to the Wallet.

Note that the catalog creation and management system will not be available in Phase 1. It will be available in Phase
2.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 243 of
252
 Dubai Islamic Bank-IT Department

11. Reports
Billers will be able to access and export reports related to their transactions, settlement and payments.

It should be noted that the reports generated by the biller will not display any source account information of the
subscriber. The reports will just display a list of transactions and whether they were successful or not.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 244 of
252
 Dubai Islamic Bank-IT Department

12. Dispute Management

Billers can raise disputes on the biller portal for various issues that may occur. Disputes raised on the biller portal will
be submitted to the PinPay Wallet Bank Portal for revision.

The types of claims that can be submitted depends on the dispute type. The types of disputes available are:

# Claim Type
1 Shortfall Settlement
2 Excess Settlement
3 Duplicate

Submitting Claims
Toto submit a claim, the biller must search and identify the transaction that has any of the above issues and select to
submit a claim. Submitted claims are automatically logged for DIB bank users to investigate and follow up on.

Closing Claims
Once a claim has been closed, the Biller Portal will display the open claim as closed with the proper narrative
available explaining the resolution.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 245 of
252
 Dubai Islamic Bank-IT Department

Agent Portal Features

The Agent Portal is a web-interface that will be provided to DIB appointed Agents to perform a number of activities
and tasks related to:

 Subscriber onboarding
 Cash in transactions
 Cash out transactions

Note that the above functions require further discussion with DIB to finalize the processes from an agent level.

This section will therefore not be included in Phase 1 of the project delivery.

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 246 of
252
 Dubai Islamic Bank-IT Department

Appendix A: List of Figures

Figure 1 - Resident Self-Registration (Pre KYC) ...................................................................................................... 1614
Figure 2- Resident Self-Registration (Post KYC) ...................................................................................................... 1915
Figure 3- Visitor Self-Registration .......................................................................................................................... 2318
Figure 4 – Resident/Visitor Back-Office Registration - Individual ............................................................................ 2721
Figure 5 - Unified Onboarding Workflow ............................................................................................................... 3325
Figure 6 - Link DIB AC/Card – Existing Users .......................................................................................................... 3828
Figure 7 - Bill Payment CASA (online bill) ............................................................................................................... 5035
Figure 8 - Bill Payment (CASA) - File Upload........................................................................................................... 5136
Figure 10 - Bill Payment (CASA) – Blind.................................................................................................................. 5337
Figure 11 - Bill Payment (Credit Card) .................................................................................................................... 5639
Figure 12 - Bill Payments (Wallet SVA)................................................................................................................... 6242
Figure 13 - Fund Wallet SVA .................................................................................................................................. 7049
Figure 14 - Unfund Wallet SVA .............................................................................................................................. 7351
Figure 15 - Closing Wallet SVA ............................................................................................................................... 7653
Figure 16 - P2P Without Fees ................................................................................................................................ 7955
Figure 17 - P2P With Fees ..................................................................................................................................... 8257
Figure 18 - Remit to ATM ...................................................................................................................................... 8760
Figure 20 - ATM Cash Disbursement...................................................................................................................... 9061
Figure 21 - CCDM .................................................................................................................................................. 9665
Figure 22 - M-POS Purchase (Scan Code) ............................................................................................................. 10269
Figure 23 - M-POS Purchase (Manual Entry) ........................................................................................................ 10771
Figure 24 - Web Checkout ................................................................................................................................... 11374 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 25 - Unload SVA Workflow ....................................................................................................................... 13795 spelling and grammar

Figure 26 - Refund Workflow ............................................................................................................................ 142100 Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Figure 27 - Subscriber Plan Creation Workflow.................................................................................................. 168126
Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 28 - Plan Configuration Workflow ........................................................................................................... 170128
spelling and grammar
Figure 29 - Merchant Onboarding ..................................................................................................................... 187137
Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 30 - Merchant Enrollment Queue ........................................................................................................... 188138 spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Figure 1 - Resident Self-Registration (Pre KYC) .......................................................................................................... 14 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 2- Resident Self-Registration (Post KYC) .......................................................................................................... 16 spelling and grammar

Figure 3- Visitor Self-Registration ..............................................................................................................................18 Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Figure 4 – Resident/Visitor Back-Office Registration - Individual ................................................................................ 21
Figure 5 - Unified Onboarding Workflow ................................................................................................................... 26 Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Figure 6 - Create DIB Profile and Wallet SVA ............................................................................................................. 30
Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 7 - Linking DIB Accounts and Cards ................................................................................................................. 32 spelling and grammar
Figure 8 - Bill Payment (CASA) ................................................................................................................................... 39
Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 9 - Bill Payment (Credit Card) ..........................................................................................................................41 spelling and grammar
Figure 10 - Bill Payments (Wallet SVA).......................................................................................................................44 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 11 - Bill Payment (Wallet SVA) ........................................................................................................................45 spelling and grammar
Figure 12 - Fund Wallet SVA Workflow ......................................................................................................................51 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 13 - Un-fund Wallet SVA Workflow ................................................................................................................. 53 spelling and grammar
Figure 14 - Closing Wallet SVA Workflow .................................................................................................................. 55 Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 247 of
252
 Dubai Islamic Bank-IT Department

Figure 15 - P2P Without Fees .................................................................................................................................... 57 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 16 - P2P with Fees .......................................................................................................................................... 59 spelling and grammar

Figure 17 - Remit to ATM .......................................................................................................................................... 62 Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Figure 18 - ATM Cash Disbursement..........................................................................................................................63
Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 19 - CCDM Workflow ...................................................................................................................................... 67 spelling and grammar
Figure 20 - M-POS Purchase (Scan Code) ................................................................................................................... 71
Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 21 - M-POS Purchase (Manual Entry) .............................................................................................................. 73 spelling and grammar
Figure 22 - Web Checkout ......................................................................................................................................... 76 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 23 - Unload SVA Workflow .............................................................................................................................98 spelling and grammar
Figure 24 - Refund Workflow .................................................................................................................................. 103 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 25 - Subscriber Plan Creation Workflow........................................................................................................ 130 spelling and grammar
Figure 26 - Plan Configuration Workflow ................................................................................................................. 132 Formatted: Default Paragraph Font, Font: Not Bold, Check
Figure 27 - Merchant Onboarding ........................................................................................................................... 141 spelling and grammar

Figure 28- Merchant Enrollment Queue .................................................................................................................. 142 Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar
Formatted: Default Paragraph Font, Font: Not Bold, Check
spelling and grammar

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 248 of
252
 249

Appendix B: Biller List

S.N SAF
o Biller Name Field name Numeric Max Characters Remarks Type Available
Special Characters should not be OnLineOnlin
1 Salik Account number Numeric Max 8 Characters Accepted e Yes
Special Characters should not be
Salik PIN Numeric Max 4 Characters Accepted
Booking number Special Characters should not be OnLineOnlin
2 Air Arabia /PNR Numeric Not available Accepted e Yes
CalenderCalenda
Departure Date r selection
Special Characters should not be OnLineOnlin
3 Fly Dubai Payment Reference Numeric Not available Accepted e No
Max 10 Special Characters should not be OnLineOnlin
4 DEWA Consumer number Numeric Characters Accepted e Yes
Max 12 Special Characters should not be OnLineOnlin
5 FEWA Consumer number Numeric Characters Accepted e Yes
Max 10 Special Characters should not be OnLineOnlin
6 SEWA Consumer number Numeric Characters Accepted e Yes
Max 10 Special Characters should not be OnLineOnlin
7 ADDC Consumer number Numeric Characters Accepted e Yes
Max 10 Special Characters should not be
8 Ajman Sewerage Consumer number Numeric Characters Accepted Off line No
9 Emaar Blind No
Max 10 Special Characters should not be
a Installment Customer Number Not available Characters Accepted
Max 50 Special Characters should not be
Customer Name Not available Characters Accepted
Max 15 Special Characters should not be
Mobile Number Numeric Characters Accepted
Max 10 Special Characters should not be
Type of Property Drop Down Characters Accepted
 Dubai Islamic Bank-IT Department

Max 10 Special Characters should not be

Unit ID Not available Characters Accepted
Max 25 Special Characters should not be
Property Details Not available Characters Accepted
b Service Fee/Maint. Fee As Installment fields & rules
c Chilled Water As Installment fields & rules
d LPF on Chilled Water As Installment fields & rules
e LPF on Installment As Installment fields & rules
f LPF on Service Fee As Installment fields & rules
g Others As Installment fields & rules
Special Characters should not be OnLineOnli
10 Emaratech Noqodi Wallet ID Numeric Max 8 Characters Accepted ne Yes
E-
GovernementGovernm
11 ent No validation required as it is passed to DIB by Merchant
12 Dubai Trade No validation required as it is passed to DIB by Merchant
Special Characters should not be OnLineOnlin
13 DED Transaction number Not available Max 8 Characters Accepted e Yes
OnLineOnlin
14 Etisalat e Yes
Max 10 Special Characters should not be
a Wasel Recharge Mobile Number Numeric Characters Accepted
Max 10 Special Characters should not be
b GSM Mobile Number Numeric Characters Accepted
Special Characters should not be
c Landline/elife Phone Number Numeric Max 9 Characters Accepted
Max 10 Special Characters should not be
d Dial-up Consumer number Numeric Characters Accepted
Special Characters should not be
e Al Shamil Consumer number Numeric Max 9 Characters Accepted

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 250 of 252
 Dubai Islamic Bank-IT Department

Max 12 Special Characters should not be

d e-Vision (Cable TV) Consumer number Numeric Characters Accepted
OnLineOnlin
15 Du e Yes
Max 12 Special Characters should not be
a Prepaid Mobile Number Numeric Characters Accepted
Max 12 Special Characters should not be
b Postpaid Mobile Number Numeric Characters Accepted
Max 12 Special Characters should not be
c Landline Phone Number Numeric Characters Accepted
Special Characters should not be
d Internet Account number Numeric Max 9 Characters Accepted
Special Characters should not be
e TV Account number Numeric Max 9 Characters Accepted
OnLineOnlin
16 EMICOOL Customer ID Alpha Numeric Not defined Min 7 Characters / no Special characters e Yes
Contract No Alpha Numeric Not defined Min 8 Characters / no Special characters

ITPMO-INI-002 Version 1.2, June 2015

Controlled Document For Internal Use Only Page 251 of 252
252