UCO Bank Aadhaar pay Merchant onboarding Flow

Sl.NO Content
1 Introduction
1.1 Document Purpose
1.2 Benefits
2 Signup procedure by the merchant
3 KYC approval
3.1 Hierarchy and role of users
3.2 Branch user journey
4 KYC rejected by branch user & merchant reupload KYC
5 Editable features access to branch user

1. Introduction

1.1 Document Purpose:

a) Provide a smooth onboarding experience without compromising on compliance with Know

Your Customer (KYC).
b) Securely scan and validate ID documents such as Aadhar cards and PAN cards.
c) Implement bank account onboarding during common onboarding.
d) To make user-friendly UI and complete KYC in 5 steps.
e) The main purpose of KYC (Know Your Customer) as an option is to establish a customer's
identity.

1.2 Benefits:
Improve business relationships.
Increased productivity.
Higher retailer engagement.
Improve data quality.
Better business strategies.

2-Self signup by merchant Procedures/Steps:

The merchant will Visit UCO Bank and the Branch user will ask Merchant to download UCO
Bank aadhaarPay Application from Play Store/Our Link.
2.1 User Journey
Step 1
Click on Create new user
Step 2
Verify mobile number through OTP

Step 3
Enable the checklists on the user consent and declaration page and click on the I Agree to
button to start the verification process.
Step 4
Click on the start KYC button to complete the KYC process.

Step 5
User needs to capture his PAN card, the PAN number will fetch automatically.
(Pan number should be editable)
Step 6
User needs to capture his aadhar front and back image the aadhar number and address will
fetch automatically.

(Aadhar number & name should be editable)

Step 6
After verifying all the KYC documents, the basic info page will open. The merchant only needs to
enter the basic details on the basic information page.
:- Following details merchant needs to enter
1. Full name
2. DOB(Mandatory)- DD/MM/YYYY
3. Business Organization name/Shop Name(Not Mandatory)
4. Turn over(Not Mandatory)
5.
 5. branch ID. (Master will be provided by UCO bank and the Dropdown option to be selected
for selecting branch ID)- (Mandatory) (fetch through Elastic API)
6. Zonal name (according to the branch ID a zonal id is also fetched. (Fetch through Elastic
API)
7. GSTIN(Not Mandatory)
8. Mobile IMEI should be captured automatically and stored in PGSQL DB & firestore.

In next Page User need to enter his bank details (as per the requirement no bank verification will
need to be done).
1. Account Number (x2)
2. Beneficiary Name
3. Bank name (elastic API)
4. IFSC Code
5. Branch Pincode

Please Find the branch master sheet in the link below

https://drive.google.com/file/d/1aWUnzn-Guxh7QlbsjeEXdawhJRdLewbm/view?usp=sharing

Step 7
After entering all basic details, user's KYC onboarding is completed
3- KYC approval through Branch
NOTE- All the pending merchants to be approved to be displayed to respective Branch user
3.1-Hierarchy of UCO bank

a) Role of zonal- Zonal Office(ZO) user can view all the pending requests of branches and can
only view no modification or approval access to given for ZO user.
b) Role of branch-Once a merchant uploads his/her KYC, It is proposed that the branch user
should have the authority to approve or reject those users based on their KYC.
3.2- Branch user jouney
Step 1- Click on common onboarding shown in the side menu.
Step 2- The user needs to select the date and time and select the status (approve, reject,
pending, reupload)

Step 3- By clicking on "I" button user KYC details will be shown to the branch user.

Step 4- Based on the KYC verification, the admin can do the needful mention below.
a) Approve
b) Reject
c) Re-upload
d) Disable
e) Enable
Step 5- After approval of KYC, a user name is created by default for the particular merchant
username have prefix and postfix code.
Username should by in this format <UCO_users's Phonenumber> i.e <UCO7763883263>

Merchants will get a welcome mail where a username is present and through the username and
mobile number, user will generate a new password.
Once the merchant KYC onboarding is approved, the branch user will assign a device to the
merchant by entering the device serial number.
4- If the branch user rejects the KYC uploaded by the merchant, then the merchant needs to
reupload the KYC details.

4.1- KYC verification Status check

The user can check the KYC verification status by clicking on “check status” in his mobile
application & verify the registered mobile number.
For example,
If the admin rejects the PAN card, the description given by the admin will show on the
application & by clicking on reupload it will redirect to the PAN verification page.
If the admin rejects the AADHAAR card, the description given by the admin will show on
the application & by clicking on reupload it will redirect to the aadhaar verification page.
If the admin rejects the KYC by clicking on ALL, then the user needs to do onboarding
again
 If the admin approved the KYC, then KYC approved page will be shown to the use

If the admin does not approve the KYC, the user will get a pending page in the application.

5- Editable features of branch user

The branch should have access to modify the below details(This can do only for Approved
Merchants), For the edit option user need to open the user profile by clicking on show user.
1. Mobile IMEI
2. Biometric device Serial Number
3. Bank Account details

Step 1
Click on show user and enter the username to show the user's profile.
Step 2
Click on "expand" to show user details, and the user can edit the details as per the requirement.

Step 3
Users can check the merchant details and assign the device to the user through the device
serial number.
The mobile IMEI number and device serial number are editable.
Step 4
By clicking on account details, the merchant's existing bank account details will fetch on the
screen, by clicking on the edit button user can edit the bank account details of the merchants.