3. Registration/Onboarding Controls

No: 202200000245

Date(g): 21/4/2022 | Date(h): 20/9/1443

Status: In-Force

Effective from Apr 21 2022 - Apr 20 2022
To view other versions open the versions tab on the right

3.1.	Member Organization should ensure registration for each phone number (or) National ID/Iqama, is linked to one application only.
3.2.	Member Organization should establish a secure process to validate users.
3.3.	The registration process should include the following:
	a.	For lending platforms: Strong form of authentication from an independent trusted party¹.
	b.	For E-wallet platforms: Strong form of authentication from an independent trusted party i.e. (National Single Sign-On (NSSO)) by using user name, password, and OTP.
	c.	For other business model, robust controls should be implemented in the registration/onboarding process taking into considerations the concept mentioned in points (3.3.a-b).
3.4.	Member Organization should verify that the ownership of the phone number is registered to the same user (i.e. match name & national ID) through trusted party only (i.e. Tahaqaq).
3.5.	Member Organization should ensure the registration process includes one-time-password mechanism (OTP) as a form of verification. The (OTP) must be send to a verified phone number as per point (3.4).
3.6.	Member organizations should implement session timeout controls for all issued (OTP)s.
3.7.	SMS notification should be sent to the users for registration, device re-registration or change in the status of account such as deactivation, reactivation and inactive.
3.8.	Member Organization application should be assigned to one- device only. Otherwise, an (OTP) should be implemented for each login, as well as disabling concurrent login.
3.9.	Member Organization should develop effective and secure process for account deactivation, reactivation and device re-registration to authenticate the user.

¹ Trusted party: Any party licensed to perform the activity in question

Soft Launch