Details of Retail User

Introduction

This option allows you to create a new retail user record.

Navigation

The following is the navigation for this option:

• Click New in the Retail User Maintenance screen.

• The Details of Retail User screen is displayed.

What you can do

The table below provides a brief description of the data displayed on the screen and the functions you can perform:

Field

Description

Bank Id

The unique ID of the bank. This field cannot be edited.

Retail User Id

The ID of the retail user to be created. This is a mandatory field.

First Name

The first name of the retail user. This is a mandatory field.

First Name (Alternate Language)

The first name of the retail user in alternate language.

Middle Name

The middle name of the retail user.

Middle Name (Alternate Language)

The middle name of the retail user in alternate language.

Last Name

The last name of the retail user. This is a mandatory field.

Last Name (Alternate Language)

The last name of the retail user in alternate language.

Salutation

The salutation to be used for the retail user. For example, Mr., Dr., Prof., and so on.

Limit Scheme Applicable

The limit scheme applicable for the retail user. You can modify the limit scheme.

Category Code

The category code associated with the retail user.

Gender

 Indicate if the customer is male or female.

Anniversary Date

The wedding anniversary date of the customer.

Email Id

The email ID of the retail user.

Amount Format

The amount format preferred by the customer. For example, Lakhs or Million format.

Date Format

The date format preferred by the customer.  The format specified will be used to print reports or display balances to the customer.

Language Id

The ID of the language to be used for communication with the customer.

Available Languages

Select the language from the list of languages available in the application.

RO Group Id

Select the RO group ID. This group ID is used by the retail user for correspondence.

Menu Profile

Select the menu profile for the retail user. The options display only retail user related menu profiles.

User's Interests

Select the interests of the user.

Multi Currency Transaction Allowed

Transaction Allowed Indicate if multi-currency transactions are allowed to the customer account.

Disabled for Transaction

Indicates whether the retail user is enabled or disabled for the transaction. As this screen is used for creating a retail user and still password is not set and user is not enabled, the retail user cannot perform a transaction, hence this field will always be Y and this is a non editable field.

Alert User Category

Select the alert user category for the retail user. This is used to send the type of alerts for the user based on the type of category.

Don't Disturb Time for Alerts

From - To

Specify the period, in hours, during which alerts should not be sent.

Address

The address of the retail user.

Address (Alternate Language)

The address of the retail user in language other than the default language.

Address for Correspondence

Specify the address for correspondence. This can be any address like residential, official, and so on.

City

Specify the city of the retail user.

City (Alternate Language)

Specify the city of the retail user in an alternate language.

State

Select the state where the customer is located.

• Click Find to view a list of State codes

• Select the state code to be entered in this field.

Note:

• The options display the States corresponding to the country.

• This is an optional field.

Country

Select the country to which the retail user belongs.

Zip

The pin/zip code of the area where the retail user is located.

Phone No.

The phone number of the retail user. (Generally this will be user’s land line number).

Mobile Phone No.

The mobile phone number of the retail user.

Fax No.

The fax number of the retail user.

Gender

Specify the gender of the retail user.

Customer Status

Specify the status of the retail user. The bank categorizes the customers as A class, B class based upon bank’s policies.

Income Range

Specify income range of the retail user.

Residential Status

Indicate the residential status of the customer.

Date of Birth

Specify the date of birth of the retail user. This must be in M/D/YY format.

Number of Household

Specify the number of house hold for retail user.

Occupation

Select the kind of occupation of the retail user.

Marital Status

Select the marital status of the retail user.

Educational Level

Select the educational level of the retail user. The bank must set the education level as A for Master degree, B for Bachelors, and so on.

Passport Number

Specify the passport number of the retail user.

Passport Issue date

Specify the passport issue date of the retail customer.

Passport Details

Specify the passport details of the retail user.

Passport Expiry Date

Specify the date on which the passport expires.

Pan / National ID

The permanent account number or National ID number assigned to the customer for payment of income tax.

Authentication Mode

The type of authentication used for activities like login and non financial transactions. Valid values:

• Password

• Secure Token

• Digital Certificate

• SMS based Mobi Token

• Device based Mobi Token

Note:

• For Password mode, the sign-on password entered by the user would be validated for authentication.

• For Digital certificates, authentication means only validating the digital certificate used by the user. The details in the corresponding screen are not sent for validation as against the authorization of the screen.

• For SMS based Mobi Token or Device based Mobi Token the passcode entered by the user is validated.

Authorization Mode

The type of authorization required.

Valid values:

• Password

• Secure Token

• Digital Certificate

• SMS based Mobi Token

• Device based Mobi Token

Note:

• For password mode, when authorization happens the user’s transaction password is validated.

• With digital certificates used and while initiating a transaction, the digital certificate is validated and digital signature is created with the transaction details encrypted and sent along with the actual transaction details. At the application server end, the actual transaction message sent is validated with the encrypted value in the digital signature. To know about the technical details of digital signatures, refer to ebanking technical document on digital signature.

• For SMS based Mobi Token or Device based Mobi Token the passcode entered by the user is validated when the transactions are initiated.